Peter,

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

Then exchange classlib for program file in my previous message. It's still your problem from not having your program files granular enough.

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

You needn't have ever asked for this project inclusion process, it has always worked like this.

You do have a chance to overcome your packaging issues by marking the pulled in files as excluded from the project.

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

How would a project hook, know which files it should include as normal and which ones are your special case files that aren't really needed?

In the long run I think you'll be better off examining your code packaging.