Hi MR. Lange

>As for the tips: First of all, get the magazine. :) Please understand that Advisor owns the copyright on the article and I can't publish it here.

Oh, understand.

>Secondly, ask yourself what you goal is, against who you want to protect and how much effort you spend on it.

I gonna sell our semi-product to foxer's company in my country (China), 95% codes/classes will be opened and well documented for them to modify for the end user. I hope to estabilish partnership and earn the $ by this means.

So, I have to protect the 5% codes/classes with a stronger methods.

>VFP is in so far an easier target as it tokenizes code and keeps variable names. .NET has a similar problem. There are obfuscators out there for .NET that make the source harder to read by replacing all names with someting like a1, a2, a3, etc. reusing existing names as much as possible.

I can search and replace all variable in base class before compile, though it's bad-feel.

And some of my points is:
- place nodefault in all save & saveAsClass
- write FLL with C++(can delphi do this?), place many fundation functions in it , call
them everywhere. The functions will do some security and license job(deal with dogie).


I think there is a way to earn dollars, but license protection is saddly must.

max.