>>Since version 5, Visual Basic can compile to 'native code'. This means, that the code generated is directly executed by the processor, instead of been interpreted by a runtime library.
>>
>>When compiled to 'native code' it is almost imposible that a decompiler can get the original source code; the most it can get is assembly language.
>>
>>So you should not worry that your program will be decompiled.
>>
>>>I have been using Refox for encrypting FPW2.6 and VFP code. It works very well.
>>>
>>>I just read about a product that creates compiled *.ASP code.
>>>
>>>That made me wonder if there exists a product similar to Refox but for Visual Basic 6.0. I am a contractor in the DFW area and VB is used everywhere but VFP very little - so I follow the flow.
>>>
>>>Anyhow, I also distribute a FPW2.6 product, NJ5J.IRS.PC.Log, at my web site http://www.nj5j.com and it is encrypted with Refox to prevent theft of source code (I also use other techinques within the software) and I am now looking at developing a product using VB6 since the product will be non-data-intensive.
>>>
>>>So, does a product exist for VB 6.0 similar to Refox?
>>>
>>>Thanks in advance.
>Ramon, thanks for the reply. I guess I am confused/concerned because on page 831 of the VB Programmer's Guide it lists the following files that are classified as runtime files and must be distributed:
> msvbbm60.dll, stdole2.tlb, oleaut32.dll, olepro32.dll, comcat.dll,
> asyncfilt.dll, ctl3d32.dll.
>This led me to believe that the exe compiled out of VB 6 WOULD be able to be decompiled; however, I am new to VB6 so I may be wrong.
>
>Thanks again for your input.
>Carl

Just search the web for "VB DECOMPILER". That should turn up a ton of hits for decompilers.