OnLoad -versus- OnOpen

[MsLady]

Please don't beat me up, i simply don't know and coudln't find anywhere with a clear explanation.

Can someone explain the difference between OnLoad event and OnOpen. They seem to perform the same function. No?

 

[Bodisathva]

don't feel bad...I've never seen a clear cut definition either. In my experience, you can have a form open (design view, normal view) and switching between the views does not trigger the open event. The on load event triggers not only when opening the form but when switching views as well.

 

[MsLady]

Thanks Bodisathva,
um i don't think i quite get it...

 

[Banana]

Consider the order events falls in when opening/closing form:

OnOpen -> OnLoad -> Activate (I think) -> OnCurrent -> DeActivate -> OnUnLoad -> OnClose

Now, because of the ordering, you can cancel a OnOpen load, but not Load (as it's already open), and you can cancel a UnLoad (because it's not removed from screen just yet) but not the OnClose.

Open and Close events has to do with "loading" the forms into the memory but they are not quite on the screen.

Load/Unload event is when forms actually shows on the screen.

Activate/Deactive is when forms has focus or lost focus.

I hope that helps.

 

[MsLady]

WOW! thanks for the brilliant explanation. That's the clearest explanation i've seen. I like how you break it down.
definately helps

Thanks too Bodisathva!!

I've printed this thread and glued it to my wall. I need to know what im doing OnLoading and OnOpening in this project im working on


thankx

 

[Pat Hartman]

There is another important point. The Open event takes place before the form's recordset is loaded so you can't use any data at that point. The Load event fires after the recordset is loaded.

There is a helpful help entry called something like "find out when events occur" which breaks down to "order of events for controls on forms", "order of events for records on forms", "order of events for keystrokes and mouse clicks", "order of events for reports and report sections".

 

[RuralGuy]

Just key in events to the Access (not VBA) help Answer Wizard.

 

[The_Doc_Man]

If you are keeping a form open and use the "navigator" buttons, you fire the OnCurrent event but not the OnLoad event.

If you perform an Update on-form and have a way to store the record, when the record has been stored, you do an OnCurrent event when you have finished the update and do the implied "Refresh" of the form.

I think of this way. If the form is a photgraphic plae and the data is the image, you fire an OnLoad when you load a plate into the camera and an OnCurrent when you trip the shutter.

Or - you do OnLoad when you build the blank form with all controls in place but still empty; you do OnCurrent when you populate it. Or REpopulate it.

 

[MsLady]

Very niceee!! Thanks guys. I appreciate all your help.

@Pat: Thanks. I found it here: http://msdn.microsoft.com/library/d...ff2000/html/acconOrderEventsRecordsFormsS.asp
Google is my friend great resource.

@RG: amaXing, i checked out too. never thought to search in access right under my nose.lol i was looking at a vba book

@ Doc: thanks for that further breakdown. You rock!

I've gotten more broken down explanation here all the same.
*printing again

Thanks all: feel free to add more if you have anything you would like to remind me. more knowledge more power!

 

[MsLady]

There is another important point. The Open event takes place before the form's recordset is loaded so you can't use any data at that point. The Load event fires after the recordset is loaded.

If you perform an Update on-form and have a way to store the record, when the record has been stored, you do an OnCurrent event when you have finished the update and do the implied "Refresh" of the form.

OnOpen -> OnLoad -> Activate (I think) -> OnCurrent -> DeActivate -> OnUnLoad -> OnClose

Okay, my lesson:

So onCurrent is what i will always use in loading my recordset...

 

[RuralGuy]

MsLady,

So onCurrent is what i will always use in loading my recordset...

I hope you just stated it wrong. OnCurrent *happens* when your form loads a RecordSet or changes records. *You* don't use it to load RecordSets; at least not normally.

 

[Pat Hartman]

The current event should be used for code that you want to run each time the current record changes. Things that fall into this category are color changes that emphasize control values and requeries for cascading combos

 

[MsLady]

Hey! Rural guy..im not that slow ...well maybe jus a little but I know it's an event
here's what i was talking about using..

Private Sub Form_Current()
End Sub

yea, what Pat said!

THANKS GUYS!!

 

[RuralGuy]

I didn't mean to offend M'Lady. Just making sure.

 

[MsLady]

okay .......

 

[ozinm]

...
OnOpen -> OnLoad -> Activate (I think) -> OnCurrent -> DeActivate -> OnUnLoad -> OnClose
...

Hi all,
Just for a bit more detail, I found the microsoft page that explains the order of events in forms, reports, etc. here:
http://office.microsoft.com/en-us/access/HP051867611033.aspx

Opening a form
Open → Load → Resize → Activate → Current
Closing a form
Unload → Deactivate → Close

 

[Banana]

Awesome; thanks for the link.

Just to be sure, though, I think the Resize event (and maybe Activate/Deactivate event, too) can fire at any other time (e.g. when it get resized or when the focus goes to another form... but not if the focus goes to another application for Activation)