Peter,

>Once more: The problem already happens if only one program file refers to one other program file. How granular can one make it?!

Do you mean PRGs with a single procedure/function in them? Or do you mean PRGs that have several procedures/functions in them? Or do you mean something else entirely?

>Do you really think that I don't know this all? I work with foxpro since 1990.

Perhaps your question two messages back was rhetorical then and I missed that.

>There are some hooks that can be helpful: BeforeBuild and AfterBuild. Furthermore, there is the Files collection. Launch a form that shows the to-be-added files, let the user make some decisions and we might undo some changes. I guess I can construct it all myself, but I have the feeling that someone else might already have done so. That's what I am trying to find out here.

You can do a delta on the files collection and give yourself a picklist of what to mark as excluded and iterate the collection and exclude them.

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