> Situation:

> We have a form (start up form) which is actually the background.
> On this form a non modal form is placed which is actually the menu.
> From this menu we open a new modal form. This new form caused a
> runtime-error (in the .EXE).
> There is no error-handling.  When the "Subscript out of range"-error
> pops up, the user can only click the OK button.  What normally happens
> then
> is that the application is ended completely, however in this case, the
> user gets to see the menu again.  All buttons can be pressed, but the
> action behind the buttons doesnt't get done.  This causes that the
> user can not exit the application.  Only an end-task seems te work.

> Has anyone got any idea how it comes that after the runtime error vb
> doesn't exit the entire application.  In develop I can simulate the
> runtime, but if chose to end after the error, than everything seems to
> exit normal.

> Many thanks.

> The absolute best thing to do is to add error trapping that allows you to either deal with
> the error or exit gracefully. Plus, fix the cause of the error (of course)

> --
> Ken Halter - MS-MVP-VB - http://www.vbsight.com
> Please keep it in the groups..

>-----Original Message-----
>Situation:

>We have a form (start up form) which is actually the
background.
>On this form a non modal form is placed which is actually
the menu.
>From this menu we open a new modal form. This new form
caused a
>runtime-error (in the .EXE).
>There is no error-handling.  When the "Subscript out of
range"-error
>pops up, the user can only click the OK button.  What
normally happens
>then
>is that the application is ended completely, however in
this case, the
>user gets to see the menu again.  All buttons can be
pressed, but the
>action behind the buttons doesnt't get done.  This causes
that the
>user can not exit the application.  Only an end-task
seems te work.

>Has anyone got any idea how it comes that after the
runtime error vb
>doesn't exit the entire application.  In develop I can
simulate the
>runtime, but if chose to end after the error, than
everything seems to
>exit normal.

>Many thanks.
>.

> Yes, you are right and I know that's the way it should be done
> normally.  But it is an application (not originally written by myself)
> which has not much error-trapping in it yet.  Placing error handlers
> in all the routines is very time-consuming.