Error handling code problem

[ijswalker]

I am trying to get this code to work but I seem to have something missing and I can't figure it out. I am trying to check it in the immediate window of the Visual Basic Editor and I keep getting a compiling error. I use the TestError (5,0) as my test.

Thanks

Ian

Sub TestError(intValue1 As Integer, intValue2 As Integer)
On Error GoTo HandleError
'declare variable to store result
Dim intResult As Integer
'calculate result by dividing first value by second value
intResult = intValue1 / intValue2
Exit Sub
HandleError:
    MsgBox "Error has occurred in your application: " & Err.Description
    Exit Sub
    
End Sub

 

[MarkK]

Maybe you shouldn't supply brackets () around parameters for a call that does not return a value?

SomeSub Param1, Param2
 - vs -
Result = SomeFunction(Param1, Param2)

 

[ijswalker]

Thanks lagbolt, you are right on the money.

Ian

 

[GRossi0511]

I'm having an issue with the same code. I should get "An error has occurred in your application: Division by zero" but instead I'm getting a "Runtime Error 11, Division by zero". I'm using the same code exactly as it is in the book. Can't figure it out?

Sub TestError(intValue1 As Integer, intValue2 As Integer)
    
    On Error GoTo HandleError
    
        'declare variable to store result
        Dim intResult As Integer
        
        'calculate result by dividing first value by second value
        intResult = intValue1 / intValue2
        
    Exit Sub
    
HandleError:
    MsgBox "An error has occurred in your application: " & Err.Description
    Exit Sub
    
    End Sub

 

[gemma-the-husky]

of course - if intvalue2 is 0, the calculation cannot be made, and causes the run time error - since anything divided by 0 is infinity (error)

note also that dividing two integers rarely produces an integer result - if you do want an integewr result you should be careful to understand the rounding that will be applied.

 

[MarkK]

You can set Visual Basic to break on all errors or to break for errors in class modules. With either setting you can have errors that occur within the scope of an enabled error handler and still, perhaps unexpectedly, break into the debugger.
In a code window check Tools->Options->General Tab->Error Trapping Section. Make sure the 'Break on Unhandled Errors' is selected.