Correct use of On Error

I`m hoping someone can explain how On Error is properly used. From what I can understand, you place the On Error before a piece of code that may generate an error. When the error is generated, the program jumps to the error handling code and deals with it. The problem I am having is how do you define the scope of the error.

For example, If I place an On Error before the code...

On Error DealWith:

Evil code that generates an error when accessing a database because of NULL

DealWith:

Code to display an error message, etc..

If no error is generated then will the program not jump to the DealWith the next time an error is generated. Also, how do you stop the code under DealWith from being executed. I really don`t understand. Perhaps I have got this wrong but should it not be more like a function with a clear beginning and end so that it is only called when an error is created. PLEASE HELP !!

You should place the errorhandling in the end of your procedure. And before the errorhandling put and exit sub/exit function/exit property, then the errorhandling will only execute when error occurs.

Resume - will return back to code
Err - is the error number
Erl - is the line were the error occured
Error Err - Shows the error occurred.

Thanks, never thought of that

Your Sub or Function with error-handling code should be structured something like the following:

Code:

---

Private Sub MySub()

    On Error GoTo SomethingBadHappened

    ' regular code here

    EXIT SUB

SomethingBadHappened:
    Msgbox "The following error occurred: Error # " _
          Err.Number & " - " Err.Description

END SUB

---

You can also use Case if you know a couple of error that may occure.

Example from the code above. In the regular code you may open a file for input.

Code:

---

Private Sub MySub()

    On Error GoTo SomethingBadHappened

    ' regular code here

    EXIT SUB

SomethingBadHappened:
    Select Case Err.Number
      Case 53: MsgBox "ops, no file with that name!"
                Resume Next
      Case Else: Msgbox "The following error occurred: Error # " & Err.Number & " - " Err.Description
    End Select
END SUB

---

To ignore the Error, use...

Code:

---

On Error Resume Next

---

If you use the following code

MsgBox Err.Number

you are going to get a runtime error

Use

MsgBox Str(Err) ' the "Number" append is not needed as is the default property.

hmmm, get errors when you are errorhandling, that's too buggy, handle those error too. Heres my opinion:
Try to avoid errorhandling as much as possible and if they are still nessesary, put them in separate procedures that you can call from your code.

The error is in the MsgBox. Want handle numerics and that is the datatype of the Err.Number. All is not lost..apparently in vb7 we get true error handling routines which bypass this "On Error" rubbish.

Jethro, I beg to differ. "Msgbox Err.Number" will NOT produce a run-time error. VB will perform "evil type conversion" and convert the number to a string (equivalent to doing the CStr yourself).

We use vb5 sp3 and it does produce a runtime error. Maybe this is not the case in vb6. I personnally know it does coz my boss (the creature from the black lagoon, Kim if you are reading this am only joking), dragged me across the coals for introducing this bug into a release version of our software.

On Error was put in to trap database connection errors. Got an error executed the MsgBox and boom runtime error. Replaced the Err with Str(Err) problem resolved.

Hmmm...should have mentioned version in original post...another arguement for adopting vb6

Str(Err) ? I don't like Str as it puts an extra space. You could avoid that with "" & Err

What about CStr(Err)?

The different between Str() Function and CStr() Function is:

CStr(expression)

• CStr will return True/False if the Expression is Boolean.
• CStr will return Date if the expression is Date.
• CStr will return Run Time Error if the expression is NULL.
• CStr will return Empty String if the expression is Zero Length String
• CStr will return Error if the expression itself have error.
• CStr will return Others numeric if the expression is number

Str(expression0[*]Str will return a string that represent the expression (If the expression is number)
and it deserve the leading space for the "+" and "-" sign.
If the number is a negative value, the it will have a leading character "-"
else is an empty space like:

Str(-123.00) = "-123.00"
Str(123.00) = " 123.00"

And Str Funtion only recognize period "."

Hence, for Err number conversion it should be the same. :)

Ok tested in vb5 sp3 and vb6 sp1, yeap your right MsgBox err & " : " & err.description does not generate an error. Therefore no need of Str(Err).

The problem l was getting was with our own ActiveX control which expects to get a string rather than numeric in a variable sMsg e.g sMsg = Str(Err) & " : " & Err.Description. This is used to display help messages and to generate a bug report form for our clients.

So you were right and l was wrong.