it seems Refox7 has another "branding" mechnism the call level 2 that doesn't just add that line of code - it also brands the vfp500.dll ... I didn't check ( yet) exactly what it does though Arnon >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 > >