I have this problem and I have tried to fix it many times.
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q242/3/47.asp&NoWebContent=1 (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q242/3/47.asp&NoWebContent=1)
is all I can find on it...is there any way I can detect where it is happing in my code? I have like 6timers and I have tried many things... I have yet to see the error but other people have had it happen to them many times. Also have seen the screen shots any idea why this may happen?
Adron: url tag
You could compile your program to native code and generate a pdb for it. Then either have your users generate a dump of it when the dialog box is up, or ask me for my vbdump.dll that generates the dump automagically. You can then load the dump into windbg and find the line that causes the error.
if I could get a copy of your vbdump.dll that would help me out alot. As of right now I am using remote admin to try and fix the problem :-/
Is that e-mail address valid?
Quote from: Adron on February 04, 2004, 03:30 AM
You could compile your program to native code and generate a pdb for it. Then either have your users generate a dump of it when the dialog box is up, or ask me for my vbdump.dll that generates the dump automagically. You can then load the dump into windbg and find the line that causes the error.
Post it here!
Quote from: UserLoser. on February 04, 2004, 04:51 PM
Quote from: Adron on February 04, 2004, 03:30 AM
You could compile your program to native code and generate a pdb for it. Then either have your users generate a dump of it when the dialog box is up, or ask me for my vbdump.dll that generates the dump automagically. You can then load the dump into windbg and find the line that causes the error.
Post it here!
I like to go slowly. If I run into any trouble with helping botmaster fix his bugs, I can adjust vbdump before releasing it to the world. I also like to have some direct feedback when releasing something new, instead of just posting it on a webpage somewhere.
That is kinda funny, using win debug for a vb application. the debug tool is insane compared to visual basic, so if your a beginner to visual basic, have fun..
But hey, everything can be learned, right?
Quote from: MesiaH on February 04, 2004, 06:42 PM
That is kinda funny, using win debug for a vb application. the debug tool is insane compared to visual basic, so if your a beginner to visual basic, have fun..
But hey, everything can be learned, right?
Yes, and it's easy to use windbg to find your VB bugs. All you have to do is check the call stack and double click to get to the failing line. From that you can usually immediately see what the problem is.