>Hi Charlie,
>The reason I want to keep each class into its own classlib is for the exact same reason you stated. To avoid having VFP pull tons of classes into a "sub-project" when I only need to use one or two classes. My .EXE is about 11MB and I was concerned about performance. Since you are saying that 42 MB is not a big deal, I won't worry about increasing size of the .EXE.

I also advocate having an app loader/launcher put the exe on the local machine. That gives a big performance boost. However, waiting for 42 Mb exe download would not be good. You could then have separate executable parts shipped to the local PC. I did that with reports, graphics and some other stuff that changed more frequently.

>Thank you very much.
>
>
>>Hi Dmitry,
>>Mike Yearwood advocated this one class per classlib and with common classes that is what I do. We have over 300 classes in a common folder. Most project specific classes are in a single classlibrary, always named the same, MyApp. Sometimes for ease of use we divide things into a few more.
>>I have EXEs that are 42 MBs, mostly because of all the template, XLTX, type files that are included. We don't have any issues with performance, so I don't really worry about the size.
>>When we first started with OOP developement we put common controls, forms, etc, into classlibrary files, grouping by type. We are still paying for that. If I reference one of the old classes, suddenly every one of those original classlibraries is brought into my project.