Jay,

>
>Well, I guess I chose a poor example. What I'm really talking about is any base framework object that contains another base framework object.
>
>Here are a couple of other examples:
>
>CBizObjMaintBaseForm contains a page frame based on the original Cpageframe.
>
>Cbizobj contains the original CDELoader object.
>
>Cfilenametextbox containes an actual (non-subclassed) textbox.
>
>I need to be able for the contained objects on these framework pieces to be able to derive from MY subclassed versions of the framework in order to have any control over them.

What Mike Levy said about Visual FoxPro is true...you can't get to these child objects that were added at design time. In Visual FoxPro you could dynamically (at run time) compose objects by instantiating a specified class, but it would be a maintenance nightmare...not to mention breaking backward compatibility.

But there is an alternate option...you can ask me to add the enhancements to the base Codebook for Mere Mortals classes for you. I have done this on a number of occasions. The current version of Mere Mortals is not only a product of Oak Leaf Enterprises efforts, but is also a collective effort based on suggestions from other Mere Mortals developers.

Regards,