>>>>>>I have a problem with my Project files. I change the properties Encrypt and Debug and 'Project File'. But these changes are not consistently remembered. A next time I initiate the project file, it again has the old settings. A remarkable finding is that the PJM file is not updated when changing the properties. (All project files are checked out.) The PJM is only updated if I choose 'Update Project'. But even then the changed settings get lost. Weird. Anyone here familiar with this problem?
>>>>>
>>>>>Back in 2.x (and maybe later), if you wanted your app to be not encrypted, but it contained an .app that was encrypted, this would force your app to be encrypted, and the settings would change on each build. Don't know whether setting the contained .app to excluded mattered any.
>>>>>
>>>>>This is at best obsolete, but since I have no other clue, best I can offer.
>>>>
>>>>AND AGAIN it occurred to me! Searching here on the UT I found this thread and, of course, the solution. I was surprised to find out that it was me back in 2005 who asked this question. Totally forgotten. Dragan, again thanx!
>>>
>>>What's the solution, then? Does exclusion of the app in the project (weird as it may sound :) solve this?
>>
>>This is kind of funny, isn't it? In 2005 you gave the clue to the solution without knowing that? :)
>
>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. 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. :-)

>>The solution is to completely remove the link to the application from the project list. As you know, that link is always 'excluded', so excluding it is not the solution. It has to be removed. If the project manager happens to pull it in again, then the solution is to make it unlocatable. That will prevent the pulling in.