"Galen Somerville" <galen@SPAM.surewest.net> wrote in message
news:uME%23fJ1LGHA.3936@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
>
>

"The Grim Reaper" <grim_rea***@REMOVEbtopenworld.com> wrote in message
news:dsn562$6ap$1@nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com...
> 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" <galen@SPAM.surewest.net> wrote in message
> news:uME%23fJ1LGHA.3936@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
>>
>>
>
>