Decompiler for VB6 Native-Compiled Applications!
 

Maybe you are aware of it:
check here: hxxp://www.decompiler.org/

They have mentioned:
"We have almost finished a Visual Basic 6 decompiler for native-compiled VB (not PCode), but now we are trying to catch up on our test data. Thanks for all the submissions we received. We now need to get the process working with the VB6 files we have received. When the process is good enough, the service can come out of Beta and go commercial.

Update (August 19th, 2004):Currently we're finishing off the decompiler. It's getting there, but it does take time. Please note: Please do not telephone us, because it is a private line. If you don't get a response via email, please email again. We don't respond to every request because we're pretty busy working on the jobs we have."

if they pretend to make a good work..i believe they should add support for PCode .. i use W32dasm for VB6/VB5 and not problems except Pcode ..

I do not know anything about decompiling Visual Basic, but heard that the native code are difficult to decompile than p-code; isn't it true? And which toold is better for vb-screwing: w32dasm or ida-pro?

for p-code try to use WKTVB debugger, it's the best. (and it's from my country) ;)

Thanks man!
but what for the "native-code compiled vb5 app"?

raja

then do it like a EXE compiled by other compiler, but you must know that the API funcs are not used else Visual Basic funcs (for example: strings use Visual Basic funcs not the API SO strings funcs).

Use SICE or IDA,etc... WDASM work very good with VB programs, search for string references and get a doc that show how the VB funcs works (there're several in the net).

In SICE make a reference to MSVB400.dll or the DLL that uses your VB version.

Good luck

Thanks Mates!