>>>>>>>>><snip>
>>>VFP debug off and "encryption" is low to no protection from even the low to average crackers simply because it can be cracked using off the shelf products. It's a no brainer. The best protection for VFP apps is probably products like Konixse and Thinstall, but even they probably only rank as a medium level protection difficulty against a true expert cracker.
>>>
>>>What, from who, for how long.
>>
>>I been following thread, and have found it an interesting topic.
>>
>>But, here is a idea that has not been discussed.
>>
>>Convert some of the subroutines (like business rules, mathimatical calculations, etc.) into a FLL library. The library is caomplied using C++ and is more difficult to decompile. This would defently up the protection of decompiling the original EXE and then recompiling it.
>>
>>Oh, and include in the library a routine that validates that the EXE is the original and not a copy.
>>
>>my 2 cents.
>
>Hi Greg. You're absolutely right. All these measures add another layer of difficulty for a cracker.
>
>The bottom line that I am trying to get across here is that one must first accept that if a cracker has your exe/app and they want the code then given the time and motivation they will get it - or a working equivalent of it.
>
>Beyond this fact one has several options for defence which range from no protecton at all up to quite reasonable protection from products like Konxise (reasonble price) and Thinstall (expensive but very cool). What level to apply depends on what you want to protect and from who and for how long.

Yes, I agree with you on this fact.

"Locks only keep honest people honest."