Hi Yuri

The problem is that the container will not be part of a form but will be used by a Web Connect app. The controls render themselves in DHTML for viewing in the IE browser. I could make it part of a form but I would have the unnecessary overhead of creating the form.

The second problem is that the controls may need to reference this property in their init methods. So it is needed before the container init fires but after the BizObj has been initiated.

Regards,
Simon



>You could use thisform.Container.BizObj instead, but if you move container, then you will get the similar problem. To avoid this you could add a form property (to refer to the container) and initiate it in the container init event.
>
>>Hi
>>
>>I am looking for suggestions from some people more experienced in OOP design than myself. The issue I am trying to resolve is how to properly get a reference to an object at the top of the container heirarchy. For example
>>
>>

>>Container
>>  BizObj
>>  CommandButton1
>>  PageFrame
>>    Page1
>>      Container
>>         Container
>>           CommandButton2
>>           CommandButton3
>>           List Box
>>    Page2
>>

>>
>>If I want to refer to the BizObj from CommandButton3 I have to do the following:
>>
>>This.Parent.Parent.Parent.Parent.Parent.BizObj
>>
>>If I later have to move CommandButton3 and this move changes the heirarchy I have to fix all the above references. I would prefer some other technique for accessing the BizObj that did not depend on the object heirarchy so that the code is more easily maintained.
>>
>>
>>Thanks,
>>Simon