Strategy for event-driven VB6/dll debug problem

Intel_C_Intel — Sat, 28 Apr 2001 03:46:39 GMT

I apologize if this is a double hit, I didn't see it on the message board after I posted. I've checked Knowledge Base and Google, both didn't have a situation quite similar to this.

I'm using a VB 6.0 driver that uses several subs from one CVF dll. The driver works in two steps, it preloads data into the VB driver, then prompts with user form to either change conditions or Calculate. After the Calculate event, the remaining dll subs are called.

From CVF Dev Studio, I can insert a breakpoint the code during the pre-load phase, and it functions normally. But when I press Calculate, the Task Manager says no response from the driver, and it doesn't break at any of the external subs (I put breakpoints on all of them to be sure).

Also, the memory usage of the compiler increases steadily at about 20-30KB per second. I can Stop Debugging (Shift+F5) and it terminates, so the compiler isn't hanging.

I've debugged from the VB side using the Debug dll, and it enters and exits the Fortran sub calls normally, but I can't view the intermediate results.

Are there any other strategies to try?
Thanks
dfh

PS. Steve, judging from your work on this board, whatever they pay you is not enough.

Re: Strategy for event-driven VB6/dll debug problem

Intel_C_Intel — Mon, 30 Apr 2001 11:52:22 GMT

This was a source code error caused by hard-coded filenames that weren't on my drive. I apologize for taking up your time--dfh

topic Re: Strategy for event-driven VB6/dll debug problem in Software Archive

Strategy for event-driven VB6/dll debug problem

Re: Strategy for event-driven VB6/dll debug problem