"Encrypted" in PJX Project Information resets

[OldxBaser]

We build our distributable EXEs with the "Encrypted" box checked in the Project Information screen. Lately, we have also checked the DebugInfo box.

We have been having an increase of C0000006 errors recently on Windows7 (64-bit) workstations on a few clients running on SBS2008(x64) networks. The VFP9Rerr.log always shows the path to the offending PRG/SCX/VCX based on the path here on our dedicated Compiler computer. (fyi the error is always on a file read).

To try and check the EXE in a hex editor for these paths, I tested recompiling with the "Encrypted" box unchecked. On a few of our larger PJXs, the build ignores the setting and compiles encrypted. When I check the setting in the PJX, it is set as checked again. If I uncheck it and exit the PJX, the next time I open the PJX, it is still unchecked, but immediately after building, it is again reset to checked.

Any ideas?

 

[Olaf Doschke]

Where do you store your pjx? File virtualisation might store changes to the virtual file store, if you put your projects within Home() within Program Files.

You better put your projects somewhere else. Into documents of your user profile as suggested by VFP anyway or into C:\Users\Public\ or on a network share.

As you say the error is always on a file read, I assume you don't mean reading of the PRG/SCX/VCX, but reading of data files, DBF or CDX. That most probably is due to opportunistic locking - a feature of SMB which you can't switch off in SMB2. And Win7, 2008 R2 or SBS2008 don't offer to revert to SMB1, where you can switch that off. Data can't reside on such systems without regular corruptions and errors.

Bye, Olaf.

 

[TamarGranor]

Does your app included any other apps? If so, are any of those encrypted? My experience is that building an encrypted app into another app always makes the containing app encrypted.

Tamar