Hi David,
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()?


>Bill,
>
>If you changed the .Height or .Width of something inside the PageFrame.Resize, or explicitly called the Resize() method of something, then it should trigger the breakpoint.
>
>Sorry for the delay I've been out of town.
>
>>There was something in the PageFrame.Resize() and each Grid.Resize() methods that triggered my Prog(1) breakpoints.
>>
>>Today, I can't get it do it.
>>I'm currently working on my Resize class, so I have code in places to test, but today everything is working the way I think it should.