Peter,

>I know that vfp has always worked this way. And I have always tried to live with this pain in the @ss. And my own applications are structured in a way that prevents this problem. (See my reply to Fabio.) But today I thought 'well, perhaps someone else has worked out another solution'.
>
>A project manager hook could be used, I guess. Probably some code that asks the developer whether the new stuff must be included as included, included as excluded or not included at all.

Sorry, it's not VFP's problem. The problem stems from the way you've chosen to package your classes into your classlibs. A little bit of rearchitecting them to be more granular and you won't have lots of unneeded code bundled into your exe.