>>{snipped}
>>>>Ken
>>>>
>>>>5.0 init helps says----
>>>>'For form sets and other container objects, the Init events for all the contained objects are triggered before the container’s Init event, so you can access the contained objects within the container’s Init event. The Init event for each contained object occurs in the order it was added to the container object.'
>>>>
>>>>
>>>>HTH
>>>>Jeff
>>>Thank you. That is a major clarification. I couldn't find anything specific to the order of loading with objects within a container. I new that events fired from the inside out, but not what order once you were inside the container.
>>
>>So let me go over this. With a form with 1 pageframe, pageframe with ,say 3, pages, and each page with its own objects, they fire like this?
>>
>>form1.pageframe1.page1.object1.init()
>>form1.pageframe1.page1.object2.init()
>>form1.pageframe1.page2.object1.init()
>>and so on until all were complete???
>
>Thats my understanding. I wonder if you changed the tab order of the objects if that would change their order. Umh ?
Well, compared to all of my other options, I think I will just copy the app stuff to another area and compile it in 5.0. At least this way I'll be able to use the better debugger, and use event tracking.
I'll fill you in on my findings.