I have a VB ActiveX dll that i am calling from a MASM32 executable using the IDISPATHC interface.

The messages go into the VB app fine.
The VB Dll can alter settings of the main app by using an export table from the exe

this all works fine when the VB DLL is compiled. However, When debugging the VB DLL in the VB IDE
It crashes every time i call an exported function of the main executable.

If i remove any calls into the main app, I can debug it fine.

any idea's

If so how can i get around it.

Posted on 2003-11-13 18:59:12 by Pliers1
Posted on 2003-11-15 12:45:47 by mrgone