>- MS, in its infinite wisdom, could "silently" cause this behaviour to break - or move it to another event/method - in a new release of VFP.
I do not agree here, because it means to change the basic event firing sequence
( Init() always goes before Activate() ) and this can break not only this approach. :)
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison