Bonnie,
I think you'll find that people who work on several disparate projects begin to break up their libraries like Nancy and I do. If you are working for a company with connected projects, each with identical UI and even data, then the larger libraries make sense.

Barbara

>Nancy/Erik,
>
>Interesting that your answers are at total extremes to each other.
>
>Erik, I assume that your class library for dataentry forms, for example, have only a few classes in it. IOW, your class doesn't contain all your forms, you limit it specifically to the type, dataentry. Correct? So then, you might have a library containing only dialog box forms, etc. and similar grouping for buttons libraries and other controls libraries.
>
>Nancy, I've considered grouping classes your way also, but wondered about redundancy. It reminds me of a discussion I had with a friend about this: there are several "types" of forms in his application. One for simple dataentry, one for forms with grids, one for dialog boxes,etc. Similar to Erik's method, each type of form would have it's own class library, but similar to your method, there would be specialized button classes and textbox classes in each of these form class libraries. Because a textbox would most likely have different properties/methods in a dataentry form than what it might have in a dialog box, for example. We never did decide which way was the "better" way of doing it, but I think he decided to build his libraries following Nancy's method.
>
>Anybody else have any comments on this???
>
>-Bonnie
>
>>Instead of collecting classes into libraries based on their class (such as all forms together, all buttons together, etc), I've started building libraries based on the idea of a unit of work.
>>
>>So, I might have (do have) one library with one specialized textbox class that get's subclassed for a number of different functions (different classlibs).
>>
>>I don't honestly know how this would affect sourcesafe issues. :-\ But, I didn't like having the situation of wanting one form from a library of forms and getting the baggage of the whole library. Where I saw this was working on existing projects and have several classlibs each with many classes and not knowing which were really used or not.
>>
>>>Hi Erik,
>>>Just out of curiousity ... how, logically, do you like to group your classes? I realize that this is a very subjective thing, and different people have different ways/reasons for grouping classes together into one vcx. I just wondered what your personal ideology was ...