In general, member objects must be contained within a parent container object to be used visually. Parent containers can contain only member objects. For example, a Page object must be in a PageFrame object to display on a Form object and a PageFrame object must have at least one Page object to be visible on a Form object. There are two exceptions:

• You can use command buttons in other containers without requiring a CommandGroup.
  
  
• Column objects can contain other controls but only one Header.
  
  

Member objects exist only as children of the parent container, which contains only members belonging to a specific base class. For example, the existence of a Page object requires the prior existence of its parent PageFrame container object. A PageFrame object can contain only pages and not command buttons.

You can associate an event when adding a new member object using the member object's count property _ASSIGN method. The member object's Init event occurs when member objects are added. However, you cannot pass parameters to the Init event of a newly created member object because members are created dynamically when the parent container's count property changes. If you need to pass parameters, you can use the container's AddObject method.

Note:
On an .scx form, if you add instantiation code to the member class's Init event, Visual FoxPro disregards that code and only the Init code for the member class definition runs. However, with visual class library (.vcx) forms, Visual FoxPro creates a true subclass. You can safely add instantiation code for other events such as Click.

Any property values accessed in the member class's Init event belong to those of the original member class. Any values that might have been overridden in the subclass are applied after instantiating the member class.

These behaviors apply only to .scx forms. After the Init event occurs, the member class is treated the same on .scx and .vcx forms.