Order of events on forms?

[John_G]

This one has me baffled.

From one of my forms, I use this code to open another one in dialog mode:

Docname = "translate form"
gbSQL_Failed = False
gbVerb_Only = False
gbUse_Keywords = False


gsCurrent_English = English
PushForm
DoCmd.OpenForm Docname, , , , , acDialog

Pushform is a procedure to hide the current form but not close it.

The problem is in the Translate Form.

According to Microsoft, the order of events when opening the form should be:

Open -> Load -> Resize -> Activate -> Current

But by using debug.print, I have found the order of events to be this when I open the form:

Current -> Load -> Current -> Open (Activate did not fire at all)

Does anyone know what's going on here? The order is backwards and On Current fires twice!

It's a pain because On Current depends on values set by On Load, but which are messed up by On Open.

Thanks for any insight.

John

[pbaldy]

Are you sure they're firing backwards, and not just displaying in the Immediate window in reverse order? I just tested with message boxes and the order was as advertised by MS (and the current event only fired once).

[John_G]

Hi -

I had the same thought - I put timings on the debug statements, and yes, they are in the order I indicated. Strange.

[pbaldy]

Can you post a sample db here that exhibits that behavior?

[John_G]

Hi -

I have to do some digging here. If I export the form to another unrelated database, and edit the code until it compiles (procedure calls, global variables etc.), then the event order is exactly as it should be. Maybe my code has some strange side-effects.

John

[John_G]

In my On Load event I had this:

Me.RecordSource = gsTranslate_SQL

By using debug.print, I found that this statement caused the On Current event to fire, so I moved it to On Open.

So, here is what is happening: (!)

On Open runs first as expected.
In the On Open, it executes this statement: Me.RecordSource = gsTranslate_SQL, which causes the On Current event to fire.

When On Current has completed, control passes back to the On Open, which then finishes.

When the On Open has finished, the On Current does not run again.

The problem is, the On Current event depends on various things that On Open does, in order to work properly.

How do I get around that one? Is there any way of stopping the On Current from running, when I have no control over it?

[pbaldy]

Is there any way of stopping the On Current from running, when I have no control over it?

I'm not entirely clear on what you're doing, but perhaps I can think of a way around that issue. You could use a form level variable, called lets say booRunCurrent. Set it to false until you want it to run, then set it to true. In your current event, test that variable and only run your code if it's true. That doesn't stop the event from firing, but will only run the code within under your controlled circumstances.

[John_G]

Hi -

That was the solution. Interestingly, the On Load event also ran inside the On Open event, probably because it wanted to run the On Current.

I had to explicity call the On Current procedure (Form_Current) as the very last line in the On Open procedure.

Thanks for the suggestions.

John


Worth knowing these subtle "features".

[pbaldy]

No problem. I've set the recordsource in the open event before, but I guess I didn't have the interdependency between events that you have.