Error Handling...

[ravynware]

What is the best and most efficient way of location exactly WHICH line causes an error? i use the on error statement most, but i have to put one on Every line until i can narrow down the error cause, is there one line/function that can do all that?

[[Digital-X-Treme]]

When you get an error, click the debug button which appears, and the VB IDE should go directly to the line which caused the error. The line will be highlighted yellow if you use the default IDE settings...

You can also set Breakpoints in your code to aid in debugging...

Hope this helps.

[ravynware]

Unfortunately my prog has a load of error handlers in it right now, a bunch of On error resume next... when i think there is an error occuring, intercede a:

on error goto newError1

newError1:
msgbox err.number & ": " & err.description
resume next

but unfortunately, when i break i go to the msgbox line, not the line that caused the error... how do i get it to go to the error'd line?

[Megatron]

One way is to remove the error handlers, and follow Digital Extreme's instructions. Once you get the line number, then you can put your error handlers back in.

[tumblingdown]

It may not help, but remember Erl.



td