>>>... as an aside, Drew Speedie had an interesting article in the March edition of FPA about Form instantiation and how to remember the order of form methods firing sequence. Her name is LISA G. Load...Init...Show...Activate...GotFocus
>>
>>That's cute, but surprisingly incomplete for something Drew would do. Even more incomplete than the VFP help topic on Event Firing Sequence!
>>
>
>Your point is well taken but that is why I started my reply with ...as an aside. Those five major events represent the instantiation of the form only and not for any other object, including the DE. The acronym was, in general, complete for purposes of the article. My apologies for not being more precise.
>
>The significance lies in that many developers mistakenly place code in the Activate that should belong in the Show, etc. This is also very helpful when you have one form calling another because, until Activate fires, the _Screen.ActiveForm is still the calling form. Therefore, I can place code in the Show, Load or Init of the child form to retrieve information from the calling form using _screen.activeform.whatever. Which I do extensively.

You don't have to apologize. I was commenting that I was surprised about Drew's article, not mad at you for mentioning it! :)

You know what else was surprising about my test? The Activate event never fired! (Again, yes, I triple checked that I have WAIT WINDOW "Form.Activate" in the Form's Activate event.) Now how can that be? Because I didn't do a read events? But the form and the button on it were active (in a wait state) at one point!

Thanks for your useful information. Sorry if I said anything that sounded like I don't appreciate your help!

Cheers,
Rich.