Hi Glen
> In summary, get in the habit of using the Init method and leave the Load alone. Our failures were in VFP 6, but I assume VFP 7 has the same problem.
>
Your comments are interesting and obviously reflect direct experience, however, let me report my own experience in this area. In more than 7 years of working almost exclusively with VFP I have never seen the situation that you describe. Nor can I recall encountering any problem that was solved simply by moving code from the Load() to the Init().

In fact, my understanding of how VFP works suggests that moving code in that direction should cause problems, not resolve them, since the Form's Init() is only fired AFTER the Init of all other controls.

Of course, I have never actually tried use the conversion tools to "convert" a production FP2.6 application into VFP (one experiment in the early Betas if VFP3.0 convinced me not to do that). Nor do I normally use 3rd party ActiveX controls in my applications.

So I am wondering if the horrendous problems that you report could have less to do with Visual FoxPro's implementation of the Load() method, and more to do with either the conversion process (which was, as we all know, very limited in its capabilities anyway) or the whole ActiveX framework (which is not particularly well known for stability either).

Either way, I am sorry but all my personal experience leads me to disagree with your conclusion to "leave the Load alone".