Hi Bruce,

The answer depends on how you structured the forms. For example, do you have more than one subform? Using a message box, you can test to see the timing of those events and which works best for you. Needless to say, in general, the master form will trigger before the subform.

Thank you Sami! I really like the idea of experimenting with a msgbox to learn, i'll give it a shot!

@ Bruce As Sami says, depending on your form design, what triggers and when can vary. For me, the sub form seems to fire first. This can be a real pain, and is for me, a significant design flaw in Access (as a sub form often needs data from the main form). Just to note, the Form_Current may fire off more than once for the main and sub forms. This can play havoc in your code depending on how complicated it is.

After discovering this, it's the primary reason that, in the ADS, I added logic to display all the triggered procedures and display them in the "status box" for developers. I hate message boxes except in a few limited circumstances.

The above image was just to open a form and bring up the first record. Can you imagine 31 message boxes? And the order in which they appeared? You can see the Activate and Focus procedures are quite active and often redundant. I have code to eliminate the redundant calls to Form_Current, so you don't see those here. Setting breakpoints is an alternative.

Uhg!

I'm going to have a longer look, but best i go upstairs right now to await the little trick-or-treaters...

Thank you for your input - the rabbit hole grows deeper-

Y'all were right, this is rather weird. I set msgboxes in empty On Load, On Current and On Active events in a parent and child.

On Active never fired in the straight opening of the parent form, but... The sequence was:
Child On Load
Child On Current
Parent On Load
Parent On Current

Really think this doesn't make a heck of a lot of sense, would think the Parent would be completely resolved except for the child and only then the child would be processed. I'm sure there is a good reason that i may just too dumb to understand, like maybe the programmer who did this did it on a Friday.

@ Bruce, in my research, it's been child and parent for decades. I've yet to see a logical reason for it.
Like I said earlier, instead of msgboxes, you can use breakpoints. Put them on the first line of every procedure and have fun watching what crazy stuff happens.