>> >Refox7 decomplies all VFP versions (and I think also FP versions)
>> >what irritates me is that we had to but it so that we can protect out
>> exes
>> >from exactly this oh well
>>
>> That means, If we want to protect our exe's, we will have to buy these
>> decompilers... Right ??
>>
>> But what if somebody comes up with another decompiler and breaks down
>> Re-fox's encryption...
>
>ReFox doesn't encrypt anything. FoxPro can decrypt the programs that it
>has encrypted, but it can't decrypt the programs that someone else has
>encrypted. This makes sense, right?
>
>What ReFox has done is allow the developer to set up a memvar to fake
>encryption. When ReFox sees this memvar, it says that it can't decrypt
>the program -- not because it can't, but simply because it won't.
>
>Of course, any other program can decrypt and reverse-compile this
>program, because it's still using FoxPro's native tokenization and
>encryption.
>
>This means that as each new program comes out to decompile FoxPro stuff,
>you'll have to add their specific memvars to your code (if they have
>one). Of course, if you write a decompilation program that ignores
>these memvars, then you'll have no problems.
>
>Gives you a good feeling, huh?
>
>/Paul

No, not at all...

Infact you have made me more worried....