G
Galen Somerville
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
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