>>It's a situation I had with one app only (a multi-module pharmaceutical wholesale warehousing app, where they insisted on having multiple modules). I don't even remember how I solved it, by recompiling the submodule as not encrypted, or by letting all go encrypted. And I never went back to it, because those were the last months of my stint in Hungary, that's end of 1995, and I never had to include .app files into a project. Later, there were other ways to communicate between modules, and other ways to make them work together, so I never tried this again.
>
>As you know, including an app isn't including it at all.

But it will try to find every file that the app uses, if it can find the app's project, and include it in the master project. Probably the reason I never tried that again.

>It is the part of the project manager I can do without. It is useless information. Actually, my applications DO consist of many many modules. And my (own) development environment is structured in a way that will prevent the inclusion of routines that are owned by other modules, e.g. by library modules. It is a pity that on each build VFP comes with the message 'Unable to find unknown {whatever}', forcing me to press [Ignore All] each and every time again. :-)

Ouch.