By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,260 Members | 1,338 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,260 IT Pros & Developers. It's quick & easy.

VB6 uses VB2005 debugger. Help!

P: n/a
I uninstalled and reinstalled VB6. When I have an unhandled exception in
VB6, it uses the VB2005 Pro debugger. There is no way to leave the VB2005
debugger without ending up at the desktop.

How can I make VB6 do it's own debugging so it shows me the statement that
causes the exception (like it always has in the past).

Anyone have the answer?

GalenS
Feb 11 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Sounds like VB6 is calling a library function somewhere (i.e. not in your
VB6 code) and the function is failing and running the 2005 debugger.
I've had VB6, VB2003 and VB2005 installed on the same machines for a while
now, and never known VB6 code to call the 2003 or 2005 debugger.

What references are your VB6 code using?
___________________________________________
The Grim Reaper

"Galen Somerville" <ga***@SPAM.surewest.net> wrote in message
news:uM****************@TK2MSFTNGP12.phx.gbl...
I uninstalled and reinstalled VB6. When I have an unhandled exception in
VB6, it uses the VB2005 Pro debugger. There is no way to leave the VB2005
debugger without ending up at the desktop.

How can I make VB6 do it's own debugging so it shows me the statement that
causes the exception (like it always has in the past).

Anyone have the answer?

GalenS

Feb 12 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.