You don't put yourself in that position if you do it and give it to the community ;-)

>I've thought about it, believe me. Only reason I haven't done it is because I really don't want to be the guy who writes the app that you're kinda forced to buy to protect yourself. I was pissed when I paid for ReFox becuase I felt I was forced to buy it in case someone else had it....I don't really want to put myself in that position with the rest of the VFP community.
>
>>What you need to do is write a program the has better decompilation protection than refox and also decompiles refoxed exes. Then everyone will have to buy your product instead of refox.
>>
>>
>>>I didn't take time to read all the replys to this, so I might be repeating some things that have been said already.
>>>Making a long story short, the answer to your question is that you can't. Even VFP apps that are 'branded' with REFOX can be decompiled. I acutally purchased a copy of REFOX at one time, and after playing around with a HEX Editor for a while I found a way to even decompile that. It did take me a fair amount of time to figure out how to do it, but repeating the process only takes me like 3 minutes. I even sent the info to REFOX (becuase I kinda want my MONEY back seeing how it doesn't do what they say).... so far they've never responded.
>>>Anyway, best thing you can do is to try to brand it with REFOX, but keep in mind that it's still possible to decompile if someone is willing to spend the time (like I did) to figure it out.
>>>
>>>>It is now a known fact that our FoxPro/VFP source code can be obtained by third party decompilation tools like REFOX. Please tell me how can I protect my software and source code so that my software doesnot get decompiled. Are there techniques or tools for this?