Hi Denis,

>That situation should have been resolved by Microsoft a long time ago. When you really think about it it's not even hard to do. It's just that they don't want to do it. Why? Beats me.

If it would be that easy, they sure would have done it. The actual problem is not that you can decompile a branded application. XiTech, and probably other companies, too, provide tools that prevent this. In ReFox, for instance, you use level 2 to encrypt the file and the runtimes.

The real issue is that the design of FoxPro is inherently flexible, but insecure. If you really want to protect applications, Microsoft has to throw out or do a major redesign that is not backward compatible for macro substitution, the EVALUATE() function, EXECSCRIPT(), the COMPILE command, VCX libraries, database events, the Config.FPW file, the FoxUser table, Intellisense, the Visual Class Designer, indexes and the DBC file. Are you sure you want that?

Christof