>One of the recent changes to the framework (Version 2.07) was to allow a developer to specify different classes to be instantiated for all of the forms that are pre-built in the framework. In the particular example you mentioned, you could subclass the About form (or create a completely new form, make the desired changes then set the application object's cFormAbout property to the name of your new form class.

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.