I
ionpopescu
I have this code in an ASP class:
If Err.Number <> 0 then
'error handling here...
End If
The code worked just fine. Now, when I debug, Err.Number and
Err.Description are empty, so, of course, as Err.number is no longer 0,
the error handling part gets executed, aborting the normal execution
even though there's no actual error in my code.
I have googled it, but the only hint I found is that this happens if
you do a "Dim Err" in your code. I haven't.
Does anybody have any idea why the Err object behaves this way, and is
there a workaround so that I do not have to change every "If Err.Number
<> 0" in my code?
Thanks,
Doru
If Err.Number <> 0 then
'error handling here...
End If
The code worked just fine. Now, when I debug, Err.Number and
Err.Description are empty, so, of course, as Err.number is no longer 0,
the error handling part gets executed, aborting the normal execution
even though there's no actual error in my code.
I have googled it, but the only hint I found is that this happens if
you do a "Dim Err" in your code. I haven't.
Does anybody have any idea why the Err object behaves this way, and is
there a workaround so that I do not have to change every "If Err.Number
<> 0" in my code?
Thanks,
Doru