>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.

Sorry that I disagree, it is VFP's problem. (You seem to suggest that I am the problem. However, I never said that I use extensive classlibraries. On the contrary, mine are all quite dedicated.)

The problem already happens if only one program file refers to one other program file.

It should be my decision whether or not that second file should be included and how it should be included. I have never asked the vfpteam to let vfp always automatically include it. I guess they expect me to thank them for the service, but must conclude that they don't offer a semi-automatic service. Suppose I would not give the users of my applications the opportunity to cancel their changes ("The changes will be saved. Are you sure?"), nobody would hire me.

Having said that, I know there is a way to make it semi-automatic: Use a project manager hook. My question was: Has anybody implemented one?