Hi!

You're correct. It does not protect, it just tells Refox about willing of protect that is not a protection.

In the Message #512733:

If the technology you going to hide costs more than expences on the decompiling, your program probably will be decompiled. When it costs less, you do not require to worry about.

That is the main point in any hacking/protection from hacking (and decompilation in particular).


>>>>>>Check this message Forum: Visual FoxPro Category: Third party products Title: Re: How to protect my VFP 6 software from DECOMPILATION Thread #511877 Message #512733
>>>>>>
>>>>>>I'm not sure, it would work, but you can try.
>>>>>
>>>>>Nadya, there is no need to check the thread. I've posted messages there myself.
>>>>>
>>>>>Once again: there is NO protection against Refox. Even the branding, in some cases.
>>>>>
>>>>>Hope this helps.
>>>>
>>>>Well, I don't have ReFox and I don't need to protect my software, since it used only in our company. Vlad's message sounds like a possible solution, that's why I gave a reference to his message. It definitely would not hurt to try.
>>>
>>>Nadya,
>>>
>>>Vlad's information is the standard code you put into anything that you want ReFox to protect. It won't do anything to stop the "patched" ReFox or stop any of the "other" de-compiling programs that are out there.
>>
>>Does it really work against ReFox? What are other de-compiling programs?
>
>It doesn't stop ReFox at all. All it is is the code that tells ReFox that you want to protect this module, that's all.
>
>UNFOXALL is one, FROG is another I've heard of, and there are probably others out there. It's a big 'net.