> 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 Seems to be so. I've had that experience with FP2.x - one single entry in the p roject file, if marked encrypted for itself, is sufficient. No matter if it's a .fxp (with or without .prg) or another .app (even if marked as excluded), it inevita bly marked whole project as encrypted. I've tried cleaning up the encryption mark manually (use the.pjx and edit the f irst record), blanking all the timestamps, and recompiling everything - FP simply fr oze after compiling first couple of routines, and I had to rebuild the .pjx from scratch. Couldn't really find other way of releasing the encryption mark, but to recompile everyt hing separately (compile *) and to rebuild the extra app without encryption, and the n it agreed to accept no encryption. I guess VFP didn't change anything for that matter. The encryption engine is pr obably the same, and probably behaves the same.