Thank you Beowulf for the suggestion..
I have intentionally not suggested dnSpy as it sometimes crashes when VB6 executables are involved.
On the other hand, Reflector is rather "mature" in the sense that it has been around for quite a while...
The approach I would suggest here would be to DECOMIPLE the VB6 dll with the VB Decompiler (available on this forum), identify the important areas of interest in the decompiled code, and then note down the RVAs of those portions, so that you can again identify them in the debugger, at runtime.
Place BP on those VAs and then check them out.
Another approach would be to change the "characteristics" of the dll to that of an EXE file and then load and debug it in olly.
Do remember that VB6 uses a"runtime" and hence DIRECTLY debugging it is rather messy, as you would getting a lot of "VM-like code of the runtime...
So, its BEST to DECOMPILE it first using the VB Decompiler before embarking on your quest ...
Good Luck
