Error Handling

[Geoff Turner]

Morning all,
Below is a piece of code to deal with a deliberate error.
Can someboby explain why, in run mode, 'errhandler'
is not reached, but the error is caught by the standard error
handler, whereas in the compiled EXE, it runs as expected?
This makes writing error handling routines difficult, since
I have to compile the app to find out if the errhandler works OK!

TIA
Geoff Turner

....code follows...

Private Sub cmdTest_Click()

On Error GoTo errhandler

Print 2 / 0

Exit Sub

errhandler:
MsgBox "Oh dear, ERROR"

Exit Sub

End Sub

[Visual Boodu .NET]

Works for me.. Code looks fine also. If you press F8 and step through the
code, what happens? What version of VB do you have? Do you have the latest
service pack?

Maybe someone else can give you ideas.

Geoff Turner wrote:

Morning all,
Below is a piece of code to deal with a deliberate error.
Can someboby explain why, in run mode, 'errhandler'
is not reached, but the error is caught by the standard error
handler, whereas in the compiled EXE, it runs as expected?
This makes writing error handling routines difficult, since
I have to compile the app to find out if the errhandler works OK!

TIA
Geoff Turner

...code follows...

Private Sub cmdTest_Click()

On Error GoTo errhandler

Print 2 / 0

Exit Sub

errhandler:
MsgBox "Oh dear, ERROR"

Exit Sub

End Sub

[Geoff Turner]

In response to your response:
Bombs out at the line ' Print 2 / 0 '
VB 6
Windows NT and Windows 98; behaviour identical on both platforms.

"Visual Boodu .NET" <[e-mail]> wrote in message
news:dZ****************@news-server.bigpond.net.au...

Works for me.. Code looks fine also. If you press F8 and step through the code, what happens? What version of VB do you have? Do you have the latest service pack?

Maybe someone else can give you ideas.

Geoff Turner wrote:

Morning all,
Below is a piece of code to deal with a deliberate error.
Can someboby explain why, in run mode, 'errhandler'
is not reached, but the error is caught by the standard error
handler, whereas in the compiled EXE, it runs as expected?
This makes writing error handling routines difficult, since
I have to compile the app to find out if the errhandler works OK!

TIA
Geoff Turner

...code follows...

Private Sub cmdTest_Click()

On Error GoTo errhandler

Print 2 / 0

Exit Sub

errhandler:
MsgBox "Oh dear, ERROR"

Exit Sub

End Sub

[Geoff Turner]

Problem solved.
Under "Tools/Options/General/ErrorTrapping" I have the option to select
"Break on all Errors" and "Break on Unhandled Errors"
Changing to the latter solved the problem.

Thanks all.
Geoff.

"Visual Boodu .NET" <[e-mail]> wrote in message
news:dZ****************@news-server.bigpond.net.au...

Works for me.. Code looks fine also. If you press F8 and step through the code, what happens? What version of VB do you have? Do you have the latest service pack?

Maybe someone else can give you ideas.

Geoff Turner wrote:

Morning all,
Below is a piece of code to deal with a deliberate error.
Can someboby explain why, in run mode, 'errhandler'
is not reached, but the error is caught by the standard error
handler, whereas in the compiled EXE, it runs as expected?
This makes writing error handling routines difficult, since
I have to compile the app to find out if the errhandler works OK!

TIA
Geoff Turner

...code follows...

Private Sub cmdTest_Click()

On Error GoTo errhandler

Print 2 / 0

Exit Sub

errhandler:
MsgBox "Oh dear, ERROR"

Exit Sub

End Sub

[Bob Butler]

"Geoff Turner" <g.********@rl.ac.uk> wrote in message news:<c5********@newton.cc.rl.ac.uk>...

Morning all,
Below is a piece of code to deal with a deliberate error.
Can someboby explain why, in run mode, 'errhandler'
is not reached, but the error is caught by the standard error
handler, whereas in the compiled EXE, it runs as expected?
This makes writing error handling routines difficult, since
I have to compile the app to find out if the errhandler works OK!

right-click on the code window, select Toggle and make sure it is set
to "Break On Unhandled Errors"