I can't work out how to intercept a second call to a function if a user
clicks a command button a second time in rapid succession. I've tried using
DoEvents but that doesn't work.
If I use a message box, that does the trick, but I don't want a message box
to appear at this point.
Using Access 2002 and 2010.

--
Bob Darlington
Brisbane

Try declaring a module-level variable, setting it to a specific value upon
first invocation, then setting it back when the function's complete. In that
way, you can check the value of the variable in the Click event.

"Bob Darlington" wrote in message
news:4e647988$0$2446$afc38c87 (AT) news (DOT) optusnet.com.au...

I can't work out how to intercept a second call to a function if a user
clicks a command button a second time in rapid succession. I've tried using
DoEvents but that doesn't work.
If I use a message box, that does the trick, but I don't want a message box
to appear at this point.
Using Access 2002 and 2010.

--
Bob Darlington
Brisbane

Thanks Douglas.
I should have thought about that.

--
Bob Darlington
Brisbane
"Douglas J Steele" <NOSPAM_djsteele (AT) NOSPAM_gmail (DOT) com> wrote

On Mon, 5 Sep 2011 17:27:12 +1000, "Bob Darlington"
<bob (AT) notheredpcman (DOT) com.au> wrote:

Actually DoEvents allows this to happen although you frequently want
DoEvents.

Also consider setting the hour glass as a psychological barrier to
waiting. Do ensure you set the hour glass back in the error handling
though. Docmd.Hourglass

Finally if appropriate, such as a recordset loop or running 10 queries
in a row, having a progress bar in your app. See the Progress Bars
and Microsoft Access page at
http://www.granite.ab.ca/access/progressbar.htm for more info.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

On 06/09/2011 03:51:41, Tony Toews wrote:
And if you feel like a pretty rainbow coloured progress meter, I have one
that I am quite happy to email to anyone

Phil

"Bob Darlington" <bob (AT) notheredpcman (DOT) com.au> wrote in
news:4e647988$0$2446$afc38c87 (AT) news (DOT) optusnet.com.au:

How quickly are you talking about? I guess it has to be slower than
the code takes to run. Would it be too kludgy to just put in a loop
to make it take longer for the function to run, so that the second
click is ignored?

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

"Tony Toews" <ttoews (AT) telusplanet (DOT) net> wrote

Thanks Tony.
I didn't understand your first paragraph.
But I'll try the progress bar.

--
Bob Darlington
Brisbane

"David-W-Fenton" <NoEmail (AT) SeeSignature (DOT) invalid> wrote

Thanks David,
I'm talking 'as fast my my old fingers will go', but some of my users seem
to do it as a matter of course.
I'll try a timer loop to see what happens.

--
Bob Darlington
Brisbane

On Thu, 8 Sep 2011 11:35:09 +1000, "Bob Darlington"
<bob (AT) notheredpcman (DOT) com.au> wrote:

If you didn't have a DoEvents in there then the user might not have
been able to click the button.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

Thanks Tony.
You were correct. I've removed the DoEvents, and the problem is gone.

--
Bob Darlington
Brisbane
"Tony Toews" <ttoews (AT) telusplanet (DOT) net> wrote