Actually, what I meant to say was to put composite controls in one or more projects, not necessarily their own separate class/project/dll. I have a project/dll that contains various generic composite control classes that are used throughout the application, by more than one of the UI DLLs. If I have a particular composite control that will only be used in one UI module, then I probably won't put it in the generic composite control project, but will keep it in that UI module's project. I can also see further breaking down a generic composite control project into several others by functionality. But, of course, this is all subjective and depends entirely on the scope and complexity of your application. KISS, right? <g>

~~Bonnie

>Hey, Bonnie...
>
>Yeah, that's what I'm doing. I have one class for all the single controls, and then another class/project for my mover container, another class for my report viewer, etc.
>
>Thanks!
>Kevin