Access Violation in VB Runtime

[kwade]

I'm having a problem that is similar to one I found on the microsoft website (Q198607) but not entirely. I have a callback function that's getting called but then dying in MSVBVM60.DLL. I'm reasonably sure that the other program started a thread and then called my callback function as stated by this problem, however, when I run it in the VB IDE, I don't get this problem. Only when I execute the .exe file from outside the development environment. This kinda makes me wonder if I indeed am seeing the problem described.

I'm looking for suggestions for getting around this problem because if VB cannot handle call back functions from another process just because it isn't in a VB thread, it's practically useless.

Any help would be appreciated. Thanks.

Kenny

[Un1]

True multithread VB5 or VB6 source code communication control:

http://www.banasoft.com/DownLoad/BNComm.exe