>>You can make it difficult to steal your source code but never impossible. A determined thief will find a way, with or without Refox.<<

A determined thief, yes; but because of ReFox, "everybody" has access to everyone's source. What goes around comes around, and "anybody" can find a "cracked" copy of ReFox on the Web.

I take exception with MS's cavalier attitude that "it's not an issue". With decompilers aimed at C, VB, Delphi and the like, the resulting code is still pretty obscure, mainly due to a lack of "names"; not so with VFP.

Visual dBase seems to be relatively secure compared to VFP; MS doesn't even have the will to "try".

Even if you buy ReFox to "brand" your code, you have to buy a "new" copy with each new release of VFP due to compatibility issues (not cheap).

I can't see why MS cannot "tweek" the encryption process so that at least it isn't so easy for ReFox to stay "current". It should be possible for programmers to seed the encryption process so that "only" a dedicated thief can hack the code vs every Tom, Dick and Harry with a copy of ReFox.