Hi all,
I have a vb6 sp5 application that works with multiple (non mdi) windows open
at the same time. If a run time error is generated, the application appears
to be terminated, but in fact it remains loaded in the memory, flagged as
locked up by the task manager. Moreover, the processor is 100% busy, making
it impossible to use the pc normally unless you first manually kill the
application or restart the pc. Has anyone ever met with a problem of this
kind? Thanks in advance
Ale
p.s. for testing reasons I DO NOT want to manage errors (not everywhere at
least)...
Ken Halter - 25 Jan 2005 15:07 GMT
> Hi all,
>
[quoted text clipped - 8 lines]
> application or restart the pc. Has anyone ever met with a problem of this
> kind? Thanks in advance
The program keeps running because there are forms, timers or external object
references that are still "alive". Despite your "PS", the only way to cure
your problem is to use error traps.

Signature
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..
Ale - 25 Jan 2005 16:27 GMT
> The program keeps running because there are forms, timers or external object
> references that are still "alive". Despite your "PS", the only way to cure
> your problem is to use error traps.
ok..ok... i hope... but...
Thanks for your time
MikeD - 25 Jan 2005 15:19 GMT
> Hi all,
>
[quoted text clipped - 10 lines]
> p.s. for testing reasons I DO NOT want to manage errors (not everywhere at
> least)...
An untrapped runtime error causes abnormal termination. It's quite possible
that some part of your app (perhaps a component your app uses which is not
destroyed due to the abnormal termination) is still in memory and executing.
Find out what's causing the error and correct it. Plus, add error handling
code. If you need to temporarily disable error handling for debugging
purposes, then just change VB's error handling option to Break on All
Errors.

Signature
Mike
Microsoft MVP Visual Basic
Ale - 25 Jan 2005 16:30 GMT
> An untrapped runtime error causes abnormal termination. It's quite possible
> that some part of your app (perhaps a component your app uses which is not
[quoted text clipped - 3 lines]
> purposes, then just change VB's error handling option to Break on All
> Errors.
I think that the problem is a vertical menu component... bah...
i try to catch error.
Thanks for your time