Not 100% sure: This may be caused by a fxp file that is already compiled encrypted. I think that if you have at least one fxp encrypted (and you don't recompile all files or you don't have the source) the EXE will be entirely encrypted.

Vlad

>I have a very large project that is Source Controlled by SourceSafe. I'm running VFP 5.0a under NT 4.0. I use Wise Install to create my installations to apply patches to the EXE for updating during this beta test period. Somewhere along the line (I don't know where or when), the check box for the project to be built encrypted got checked. And now it''s stuck. I go into the Porject Info dialog, uncheck encrypted, rebuild the exe adn low and behold, encrypted is checked angain. I even went into the PJX and mark it .F., rebuilt from command line, and encrypt is .T. again. Arrrgghhh....
>
>This has produced a major problem for me and my beta testers. When VFP encrypts the EXE, you can build the same project twice (with no changes) and you get 2 different exe's. They are the same size, by the contents are not the same byte for byte. This has been verified by utilities that compare files and when you do this you get very long lists and sometimes the message, "too many differences to list".
>
>Now here's my problem, Wise has an add-on for creating patches. At this point in the development process, updates go out very frequently but with minor changes. I used to be able to create setups with patches and they would always be less than 1M. The EXE size is around 5M. Now that the EXE is encrypted, Wise can no longer patch the file becuase it's too different from the previous version and it incldues the entire file. Now my setup is in the range of 4-5M. This is a big PITA for people who download the updates with Dial Up Networking. 5M at 28.8 is painful to say the least.
>
>Any help or clarification on this matter would be greatly appreciated.
>
>Thanks in advance.