David,

You fixed a similar problem for me (well, told me why and how to fix it) for the Moved() event, so I'm not going to doubt you here.

But this case (Resize() does seem odd - I mean, isn't the most likely case that .Height and/or .Width are modified on most controls on a form?

It seems extraneous in the extreme that non-default Height/Width would trigger Resize(). Why do you think it does this?

cheers, and Happy New Year.


>Bill,
>
>If you set the .Height and/or the .Width on the property sheet, that will trigger the Resize() event before the Init() fires. The property sheet values are assigned to the object as one of the first things that happen during the object construction. The Init() event fires at the end of construction, at this point the object is all ready to go.
>
>>I've seen it happen again. I can't figure out why it sometimes happens and sometimes doesn't.
>>For some reason, the Resize() events of ALL objects in the form are executed BEFORE ANY init() events.
>>
>>My event sequence when I start a form is:
>>1. Form.DataEnvironment.BeforeOpenFiles.
>>2. Form.Load
>>3. Form.PageFrame1.Page1.grd1.Resize
>>4. Form.PageFrame1.Page1.grd2.Resize
>>5. Form.PageFrame1.Resize
>>6. Form.PageFrame1.Page1.grd1.Init << First Init()
>>7. Form.PageFrame1.Page1.grd2.Init
>>8. ......
>>These are ALL Prog(1). I didn't look at any Prog(2).
>>
>>All those Resize() events have code in them, but NOTHING has been Init() yet.
>>
>>I see that every one of those objects have a non-default setting for .Height or .Width, and I'm guessing that is what is triggering the Resize(), but why execute EVERY Resize() before ANY Init()?