Hi Dave,

Thanks for providing me with a better understanding on this subject. I figured there were good reasons for not being able to modify class definitions through the form designer. Know that I know why, it's much easier for me to live with.

Thanks again,
Frank



>Frank,
>
>>Can someone clue me in. When working in the form designer, you can add properties and methods to the form through the "form" menu pad option, but you can't do the same for objects contained within the form. You have to first save the contained objects to a class, get out of the form, then go through the class designer to add custom properties and methods. I'm just wondering how come custom properties and methods can't be added to contained objects through the form designer.
>
>>Is it because it would foster bad design?
>
>Basically yes. If an internal object ought to have some custom properties they ought to be created at the appropriate level in that class' inheritance hierarchy.
>
>Forms aren't really any different than the class designer. If you are creating a container class of some sort and you drop objects into this class you can not add properties/methods to those internal objects either. Both the class and form designers only allow you to add properties/methods to the outermost item in the designer.
>
>>It seems to me building quick prototypes would go much faster if this capability existed in the form designer. Or is my thought process just a??-backwards
>
>It's not really that hard swapping between the class designer and the form designer. The only problem that you can't open the class designer if you have the form with an instance of the class at the same time. It's only a "little" un-RAD.