>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

Your terminology is correct.

Separation into libraries for those reasons is sound.

But why so many classes? You might be better served to add custom properties that can be set at the instance level and write generic code in the super-class to handle it. If you post some examples of why you're going with this many libraries, I can probably suggest some ways of genericizing it. If I can't, someone else probably can.

HTH