macro execution - timing of events

[dpimental]

If I have a macro that does a number of things (e.g., sets warnings to false, runs some update queries, delete queries, insert queries, sets warnings to true, then finally opens a form). If the last thing that is being done is to open a form, and the form remains open, does that mean the macro is still running?

When does it stop running, when the form is closed?

David Pimental
(US, Oh)

 

[SkipVought]

Hi,

If the last thing that is being done is to open a form, and the form remains open, does that mean the macro is still running?

One of the last statements in your macro is something like...

YourFormObject.Show

If not other macro is called after that statement, the macro is done.

Skip,

_{Just traded in my old subtlety...
for a NUANCE!}

 

[dpimental]

So, to clarify, once the last command is executed in a macro, it's done, correct?

One last question is, what if you have an openform command, and then after that command, you have a setwarnings to true command?

David Pimental
(US, Oh)

 

[SkipVought]

It's done.

Skip,

_{Just traded in my old subtlety...
for a NUANCE!}

 

[SkipVought]

Are you actually referring to a MACRO or a VB Procedure?

Either way the form is opened or closed and thats it. Nothing is waiting, unless you have code with a "DoEvents loop".

Skip,

_{Just traded in my old subtlety...
for a NUANCE!}

 

[dpimental]

Cool, thanks for the clarification.

I had a macro I was updating and noticed that they were actually calling a macro, right before setting the warnings back to true.

All the macro did was open a form. So, I was thinking of replacing the macro call with a simple open form call.

David Pimental
(US, Oh)