As far as I know, there is no way to prevent the user "clicking ahead". The
only thing I can think of is to discourage this behaviour by setting the
mouse pointer to an hourglass for the duration of the operation.
However, I will do some more research to see if I can find a way, or perhaps
someone else might jump in here with a solution, so check back on this
thread in a couple of days for any updates :-)

Signature
Good Luck!
Graham Mandeno [Access MVP]
Auckland, New Zealand
> Sorry Graham. Was out for a day.
>
[quoted text clipped - 20 lines]
>> > are
>> > taking place?
Still no known way to *disable* the click-ahead, but here are a couple of
possibilities:
1. Create a small form with a label on it: "Please wait... updates in
progress...".
Put your code into the form's Load event, and when the code is complete,
have the form close itself.
When you want to run the code, open the new form modally (by specifying
WindowMode:=acDialog)
2. Suggestion by fellow MVP Ken Snell:
Put a "big" command button (transparent) over the entire area of the
form
(or over the command buttons). Make the button invisible initially. When
your code begins running, the first thing to do is make the transparent
button visible and bring to front. With no event procedures on the
button,
the user can click all he/she wants and nothing will get through. Make
the
button invisible when the code is done.
3. Suggested by Ken Snell and "Sco" Scofield:
Have the code disable the buttons as its first step, and then
enable them when done. You could loop through the controls (use Tag
property value or control type).

Signature
Good Luck!
Graham Mandeno [Access MVP]
Auckland, New Zealand
> As far as I know, there is no way to prevent the user "clicking ahead".
> The only thing I can think of is to discourage this behaviour by setting
[quoted text clipped - 29 lines]
>>> > are
>>> > taking place?
faberk - 08 Apr 2005 03:43 GMT
Interesting. Thank you gentlemen. Very much appreciated.
> Still no known way to *disable* the click-ahead, but here are a couple of
> possibilities:
[quoted text clipped - 55 lines]
> >>> > are
> >>> > taking place?
Ken Snell [MVP] - 08 Apr 2005 03:43 GMT
Slight modification to #1. The form that you open needs to have its Modal
property set to Yes in the form's design view when you create the form. Then
it should be opened "normally" (WindowMode should be left empty as an
argument). Dialog mode will stop your code from running.
(thanks for the plugs, Graham! :-) )

Signature
Ken Snell
<MS ACCESS MVP>
> Still no known way to *disable* the click-ahead, but here are a couple of
> possibilities:
[quoted text clipped - 57 lines]
>>>> > are
>>>> > taking place?
Ken Snell [MVP] - 08 Apr 2005 03:48 GMT
I cancelled a reply that I made to Graham's post, but in case it doesn't
cancel before everyone sees it, please ignore that post.... I misunderstood
what Graham wrote (I read too fast!) and my post is "not on point" to his
suggestion!

Signature
Ken Snell
<MS ACCESS MVP>
> Still no known way to *disable* the click-ahead, but here are a couple of
> possibilities:
[quoted text clipped - 57 lines]
>>>> > are
>>>> > taking place?