J
John Lane
How can I stop in-line code execution after a Docmd.OpenForm? Thanks.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
O
Ofer
Open the form as Dialog, will halt the code until you close the form
docmd.OpenForm "FormName",,,,,acDialog
docmd.OpenForm "FormName",,,,,acDialog
M
Marshall Barton
John said:How can I stop in-line code execution after a Docmd.OpenForm? Thanks.
Open the form in dialog mode:
DoCmd.OpenForm "formname", . . ., _
WindowMode:= acDialog
O
OfficeDev18 via AccessMonster.com
Sorry, guys, acDialog will NOT stop code execution from continuing in the
calling module, although focus will be stuck on the newly-opened form.
The only way to stop execution is by opening the new form - I concede that
acDialog is a good idea - as the last functional line of code in the calling
module (meaning it can be followed by End Function or the like, but not any
new processing).
HTH
calling module, although focus will be stuck on the newly-opened form.
The only way to stop execution is by opening the new form - I concede that
acDialog is a good idea - as the last functional line of code in the calling
module (meaning it can be followed by End Function or the like, but not any
new processing).
HTH
R
Rob Oldfield
errrmmm.... yes it does.
OfficeDev18 via AccessMonster.com said:Sorry, guys, acDialog will NOT stop code execution from continuing in the
calling module, although focus will be stuck on the newly-opened form.
The only way to stop execution is by opening the new form - I concede that
acDialog is a good idea - as the last functional line of code in the calling
module (meaning it can be followed by End Function or the like, but not any
new processing).
HTH
J
John Lane
I tried acDialog and it didn't stop inline code execution. Here's how I did it:
Global_Gate = 1
DoCmd.OpenForm "AlreadyImportedWarning", acNormal, , , acFormReadOnly, ,
FileName
Do While Global_Gate = 1
DoEvents
Loop
The Do loop localized it and the DoEvents gave time back to the operating
system so the opened form got time to also execute. Then in the opened form's
Close event I open the gate (set it to 0). Works great.
Global_Gate = 1
DoCmd.OpenForm "AlreadyImportedWarning", acNormal, , , acFormReadOnly, ,
FileName
Do While Global_Gate = 1
DoEvents
Loop
The Do loop localized it and the DoEvents gave time back to the operating
system so the opened form got time to also execute. Then in the opened form's
Close event I open the gate (set it to 0). Works great.
M
Marshall Barton
Well, that will work, but it's the long way around the
problem. I am more interested in the acDialog you tried
that didn't work. Could you post that code so we could see
the circumstances that are forcing you to use a less than
optimal approach?
problem. I am more interested in the acDialog you tried
that didn't work. Could you post that code so we could see
the circumstances that are forcing you to use a less than
optimal approach?
A
Albert D.Kallal
OfficeDev18 via AccessMonster.com said:Sorry, guys, acDialog will NOT stop code execution from continuing in the
calling module, although focus will be stuck on the newly-opened form.
No,the above explains a model form, which is MUCH different then a acDialog
form.
The only way to stop execution is by opening the new form
Hum....that is exactly what everyone is saying!!...Open a form in
acdialog..and the code will halt.
In fact, using acDialog forms is one GREAT way to build prompt forms that
can RETURN values
without having to use global vars.
I explain how this works here:
http://www.members.shaw.ca/AlbertKallal/Dialog/Index.html