Hi,

I am just trying to figure out why this is happening to FORM when converted to a class. I have a lot of forms that can be converted into classes. I am trying to get feedback as to the best practice approach to do the conversion, what to avoid and what are the correct way of doing things in OOP. There will be a hell lot of changes to do now but as someone told me that in IT the only constant is change. Thank you again for the help.

Regards,
Kueh.

>>Dear David,
>>
>>I do not use the data environmnent and my controls are not bound to any controlsource. My problem is that any command in the INIT method that reference "thisform.pageframe.page1.textcontrol.value" would cause an error. When I take a look in the Debugger the object can only be evaluted up to the "thisform.pageframe" level and beyond this it seems that it is not initialised yet. Strange since the INIT method is called from the "textcontrol". BTW the control that I have is a text box that itself is a subclassed. Could this be the problem?. Thanks.
>>
>
>>>>I have form that has a pageframe and this works fine if i call it via the "Do FORM". Since I have save this form as a Class. I get error in the INIT method of object inside the pageframe complaining that the pages object does not exists. Can someone help me here? Thanks.
>
>What you're seeing has nothing to do with classes and subclasses and everything to do with order of instantiation. INIT() occurs from the inside out. That is to say, even though the page.Init() has been triggered, it does not complete until *all* of the objects on that page finish their Init(). IMO, it happens counter-intuitively, and that's why it's confusing at first... sort of like saying I can have a glass of water without the glass... but it makes sense in the OOP world.
>
>What, exactly, are you trying to accomplish?