>>>1. You can add container class to the page frame in run-time (the technique we're using - delayed instantiation of the objects not needed - saves form's activation time).
>>>
>>>2. You can have a special container class with common code and properties. That's also what we're using.
>>
>>I tried the saving the objects as a class on one of the forms and it worked great. If I have 3 forms to save as 3 separate container classes, how do I get them to all be based on a special container class. Will I need to hack the vcx and change the class they are based on?
>
>Yes, I always do this kind of things by hacking. Someone (Marcia?) had recommended a tool in the past, do you want me to try to find this message?
>
>I do it by hand, when needed.

No, I think I have it somewhere. Works for forms and classes.

Ok, my (maybe) last question has to do with time to start the form. In reading what someone else just posted, it increases the load time to have all that stuff on one form, but it sounds like what you are saying is that by having them as classes, the instantiation of the form would be reasonably quick. Is that true? I didn't really understand what you meant by delayed instantiation though.