I have tried 1 extreme to another. When I provided forms [SCX] and classlibs [VCX] separately, performance started off good but gradually declined to the point of most unacceptable. When I compiled all the forms and classlibs into a single EXE, performance returned and remained high. I am not sure why this was and maybe it has changed since VFP 6 when I last tried this. I am not very willing to try this experiment again.

I did find a compromise. My main app is compiled into 1 EXE which calls a separate REPORT.APP module when they need to run reports. You could do something similar. However, some "inclusion duplication" may be required in your separate projects. For example, common classlibs used by forms in multiple projects may have to be included and compiled into all these projects. The component APP/EXE will still be smaller so that is good. IMHO, maintaining separate components is easier and more lightweight when providing updates.


>The Boss in my company has communicated he would like a "component" based system for the following reasons:
>
>1) Possible to create different forms for customers
>2) Possible to release a fix in one form without introducing other problems by including other changes at the same time.
>3) Reduce Exe size and increase performance
>4) Ease Testing Burdon on the application and reduce the number of bugs.
>
>The idea could be something like a folder containing all frx files (maybe compiled into app files) plus the core exe file.
>
>When I click a button to open a form the form the correct app or frx file is launched off the disk.
>
>This is departure on the current 1 (huge) exe for the application approach.
>I have a feeling its going to be a nightmare myself but I thought I would open up the discussion for anyone here.
>
>So if you have any pros/cons/ideas/advice on this subject please let me know.
>Thanks
>Tim