Thanks for the advise! I'll give that some thought. The reason I was making a base class "form" is because we had several forms that were very similar, so we made a base-class with all the common controls, then subclassed that to make the final forms to avoid duplicate work. Is this a bad aproach?

>>I've got a strange problem. I've got a base class containing various labels, TextBoxes, buttons and a PageFrame with 6 Pages. I've got another class that inherits from the base class. When I change componants on the Pages in the base class (resize things, moving controls around on a Page, etc...), the class that inherits from the base class changes appropriately. But when I change the Page Order of the pages in the base class, the inherited class does NOT reflect the changes.
>>
>>Any ideas?
>Lee,
>
>I cannot tell why the pageorder is not inheriting. I can tell you that you are header down a design road that has lots of traps and land mines in it. Ths is because you are subclassing compound classes and this causes problems. It is a much sounder class design to build each control as a class and subclass that as needed, build a pageframewclass that has NO CONTROLS in it and subclass that as needed, then as the last class definition before creating an object compose the finished pageframe by putting the controls in it. This is referred to as late binding and is much easier to evlove in the future.
>
>The traps will lie if you try to modify the code in one of the controls in one of the pageframe subclasses, the calls to the "inherited" code will not work properly. Also if you go back to the parent pageframe and remove something then go to the subclass you get situations where the subclass will not open with an error and you're skunked.