>- 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. :)