There are definately some quirks to composite classes, and if you want to use them, you should read the article Drew Speedie wrote for FoxPro Advisor in Feb 1998 called "Dangers of Composite Development". If you keep your composite classes very simple, like the example you posted, you should run into many problems, but you should still be aware of the issues.

>I hope I'm using the correct terminology, so everyone can understand my question, but I started in Delphi and don't always use the VFP terms.
>
>What are the implications of creating a libary with sub-classed controls(like a combobox whose rowsource is Yes,Y,No,N), creating a container in some library and adding a label and the cboYesNO control for every situation where I need to allow a user to respond. (Our design team has chosen not to use checkboxes in most cases.) I envision maybe 500 - 1000 of these classes in various libraries. In creating libraries, I'm attempting to only include those controls that are fairly specific to mitigate the inclusion of classes in an app that are not required.
>
>TIA