Continue after error & Application.Thr eadException

[Matthew Hood]

I have a DLL I created to handle all unknown errors using the
Application.Thr eadException event. I'm asking the user if they want to
terminate the program or continue. This is working like I want. The
program exits when I tell it to terminate, and when I continue, the program
keeps running but the routine that generated the error exited. I want to
take this a step further though. Instead of the routine that generated the
error exiting, I would like it to continue with the next line, or even retry
it if possible in some circumstances.

Any ideas on how to accomplish this?

TIA,
-Matt

[Herfried K. Wagner [MVP]]

"Matthew Hood" <Dr***********@ Yahoo.com> schrieb:

I have a DLL I created to handle all unknown errors using the
Application.Th readException event. I'm asking the user if they want to
terminate the program or continue. This is working like I want. The
program exits when I tell it to terminate, and when I continue, the program
keeps running but the routine that generated the error exited. I want to
take this a step further though. Instead of the routine that generated the
error exiting, I would like it to continue with the next line, or even
retry it if possible in some circumstances.

You could use 'On Error Resume Next' inside the method directly. Notice
that this will maybe prevent the 'ThreadExceptio n' from being thrown.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[Jay B. Harlow [MVP - Outlook]]

Matt,

take this a step further though. Instead of the routine that generated
the error exiting, I would like it to continue with the next line, or even
retry it if possible in some circumstances. Any ideas on how to accomplish this? Unfortunately there is no "easy" way to do this, as by the time the
Application.Thr eadException handler gets the exception the stack is
completely unwound.

The "best" you could do is to put a Try/Catch around each of the commands
you want retry and have the Catch block retry the Try Block. I find using
Goto in the Catch block the "easiest" way to "Retry".

Something like:
Try Retry:
'...something

Catch ex as FileNotFoundExc eption

If MessageBox.Show ("File does not exit!", _
Application.Pro ductName, _
MessageBoxButto ns.RetryCancel, _
MessageBoxIcon. Question, _
MessageBoxDefau ltButton.Button 2) _
= DialogResult.Re try Then
GoTo retry
End If

End Try
Instead of the Goto, others have put the entire Try/Catch in a loop...

Hope this helps
Jay

"Matthew Hood" <Dr***********@ Yahoo.com> wrote in message
news:Of******** *****@TK2MSFTNG P09.phx.gbl...I have a DLL I created to handle all unknown errors using the
Application.Th readException event. I'm asking the user if they want to
terminate the program or continue. This is working like I want. The
program exits when I tell it to terminate, and when I continue, the program
keeps running but the routine that generated the error exited. I want to
take this a step further though. Instead of the routine that generated the
error exiting, I would like it to continue with the next line, or even
retry it if possible in some circumstances.

Any ideas on how to accomplish this?

TIA,
-Matt

[Cor Ligthert]

Jay,

Instead of the Goto, others have put the entire Try/Catch in a loop...

Exactly saves me to write it?

Thanks

:-)

Cor

[Matthew Hood]

Thanks for the responses. The On Error is a no-go. I already got Try/Catch
statements around areas I know COULD cause a problem though I didn't think
about using a goto to try again. Not sure how this could be used in my
applicatoin.Thr eadexception handler though.

Thanks again.
-Matt

"Matthew Hood" <Dr***********@ Yahoo.com> wrote in message
news:Of******** *****@TK2MSFTNG P09.phx.gbl...

I have a DLL I created to handle all unknown errors using the
Application.Th readException event. I'm asking the user if they want to
terminate the program or continue. This is working like I want. The
program exits when I tell it to terminate, and when I continue, the program
keeps running but the routine that generated the error exited. I want to
take this a step further though. Instead of the routine that generated the
error exiting, I would like it to continue with the next line, or even
retry it if possible in some circumstances.

Any ideas on how to accomplish this?

TIA,
-Matt

[Cor Ligthert]

Matthew,

When you see my answer above yours to Martin Ho (when the messages are
sorted on sent date) than you can see a sample of my using it in a loop and
a try and catch block.

Cor