This thread is for discussions of "On Error Resume Next" considered harmful.

"on error resume next "  is a life saver for minnor runtime errors its saved me plenty of times

I think the main problem is that it can easily hide major ones too, without you even realising  

Fortunately, with VB.NET we can choose to ignore particular errors, and throw others

I am Guhan from Srilanka.

I am just nothing compared to your knowledge and experience sir.

But what I learned in my MCP curriculum is that you use the "On Error Resume Next" statement in a technique called "Inline Error Handling". That is you should use the statement where you think the error would occur and that you should check the error number of the Err object immediately after that statement to determine the status.

I hope that nothing will go wrong if we keep track of errors, rather than just putting the "On Error Resume Next" on the top of the event handler code.

I like to know if I am wrong on this matter sir.

Thanking You,
Guhan.

Hi Guhan,
Of course, if you'd use "On Error Resume Next" and if you DO check the Err variable after each statement that might generate an error, then yes, there is nothing wrong with that. The problem with this inline approach is (like the article said) that it is just too easy to forget the checking. The structured exception handling using 'Try Catch', while having its own quirks, is far more robust, elegant (and modern;-) that the inline approach.

Just my $0.2

Palo

Hi Palom,
Thank you very much for the reply. I agree with what you have said.

- Guhan

I have a simmiliar experience using ASP. The when there is error when creating recordset, the recordset will loop forever. Interestingly this happends on every machine except one machine. On that machine the error successfully trap. I have been trying to find is there any settings on IIS or SQL Server cause this. Any idea?