Gary,
I'm unclear on your reasoning for wanting to put these containers into a form class. Why not leave them as containers which can then be dropped onto a page of a pageframe or onto a form for 'single' instanciation. Drew's comments on subclassing controls in forms (or at least when I heard him speak at a couple of meetings) concerned being aware of the hierarachy of subclasses in a subclassed container, NOT that you shouldn't ever do it.

For example, if you design a container using your own subclassed textboxes, and then subclass the container, any change in your textbox class will be reflected down the line of container subclasses. However, if you subclass both a container AND the textbox class IN the container separately, a change to the latter would NOT be reflected on your container. The container hierarchy does not include the new textbox subclass.

Drew made this distinction to show why you should subclass his components separately from the Visual MaxFrame classes instead of subclassing his example forms.

HTH
Barbara

>My pageframe class allows for a container class to be instatiated at run time containing the page controls. This is to avoid the instantiation overhead commonly associated with pageframes. I believe this is a recommended technique and is the approach adopted by my third party framework.
>
>On certain occasions, the pages on the pageframes are in effect representations of application classes. One page may have client information, another page vehicle information, another page driver information and so on.
>
>Could anyone advise the best approach to develop these classes in the guise of a .VCX form, so they can be subclassed for specialised purposes, but have them "loaded" in the containers on the page(s) of the pageframes?
>
>I understand that sublclassing "containers" containing controls is not recommended. Apparently, the container is subclassed but not the controls in it (Drew Speedie - FPA some time ago).
>
>I don't even know whether a "container" can contain a form (itself a container). Before I dive headlong in to this, I would very much appreciate some theory/design advice.
>
>TIA