CODEWITHSUNDEEP
vb6crashexecutable
JP Berrocal
JP Berrocal

Reputation: 145

Vb6 application works in the IDE but the executable crashes

I have a little problem with visual basic 6 project. Everything works fine in the IDE but the executable crashes every time, when I run the application. The application uses callbacks to communicate with a C++ dll. Even code as simple as showing a message box fails when the callback starts.

I changed the compilation mode to P-Code and still the problem persist.

Any help would be appreciate.

Thank you all

Upvotes: 5

Views: 2504

Answers (4)

Karl E. Peterson
Karl E. Peterson

Reputation: 771

This sounds like the callbacks may be occurring on a different thread than your application is executing on. [EDIT: As I see Jim has already suggested.] If that's the case, yeah, kaboom just as soon as you "touch" anything OLE related or call into the runtime. Same story as with multimedia timer callbacks, fwiw, and I'd suspect you'll have to take the same precautions as one would with those if this is the case.

The short story with different thread callbacks is that you'll need to post a message to yourself, using PostMessage declared in a typelib so that the Err object isn't set by VB, then let the callback return. You do your own processing on receipt of the posted message. Here's the typelib I used for this with the CCRP Timers library:

http://vb.mvps.org/tools/files/postmessage.zip

Hope that helps...

Upvotes: 3

OneNerd
OneNerd

Reputation: 6552

A few questions:

  1. Is the executable on the same PC as it was developed, or a different one?
  2. Does the file use a manifest file? If so, does mainfest call XP themes?
  3. Also, if using manifest, does manifest use SXS for OCX files?

Upvotes: 0

Jim Mack
Jim Mack

Reputation: 796

Who's calling back to whom? Show us a little code.

The IDE can mask real problems, so just being able to run there is no guarantee that what you're doing is supported.

One common problem with callbacks is that VB6's runtime is not thread-safe, so if another thread is calling back into your VB code, you can't do anything that will invoke the runtime -- like access strings or objects.

There are ways around some of these issues, but I think we need to know more first.

Upvotes: 1

RiddlerDev
RiddlerDev

Reputation: 7479

Is the code being run from the same location as the IDE? Likely it is a reference problem, and you need to re-register the DLL.

A deployment package should make sure you have everything installed.

Upvotes: 0

Related Questions