Erik's comments were very good. Another reason for keeping classes in several VCX files is to allow several people to change classes. If you're using Visual SourceSafe (or similar version control) only one person can check out a library to work on it. If you have several developers and are not using version control or at least not locking files into it, then several small vcxs allow developers to make changes without overwriting another's work.

Barbara

>I have collected quite a few classes. I was thinking of subclassing them all into a large class file in a shared directory in my development environment (as a sort of component repository). Then I would subclass just the classes I need for a specific application into a class that lives in a specific application directory. Does this make sense? Or should I split all my class files into some type of grouping. I guess my main question is: when you build an app that includes large class files containin classes that are not used, is there a performane penalty?