I know what you're saying. It just makes me hesitant to use (subclasses of) the VMP composite form classes, for fear that 2 years from now I may need some unusual logic for a particular control. If that happened, I'd have to change each subclassed composite form class, rather than just changing the subclassed version of the control... Yet I yearn to use the composite form classes in the interest of time.

Would you recommend not using the VMP composite form classes? Any input would be appreciated. Thanks -- Sue


>Hi Susan
>
>You can't hack controls that are included with the form (as a composite class). That would be like performing magic on a heart patient's heart to make it inherit from a pig or some other animal.
>
>Hacking can alter the inheritance structure of an object. So, if the form you are looking at inherits from frmDEGridNav2Pages, you could hack it to make it inherit from frmXXDEGridNav2Pages.
>
>If you added a txtBase to a form and later decided it should have been a txtPicklistValid, you could hack that txtBase and change it to a txtPicklistValid.
>
>If we go back to the heart analogy, you can add a pacemaker and magically change the type of pacemaker, but the heart came with the patient and you can't change it easily.