>>>>Because it is a new thing you have to learn. Why should I be forced to learn something new when an ON ERROR can be made to work just as well as it did back in the dBASE days?
>>>>(or at least that's how I interpret reaction I've seen from some folks)
>>>
>>>I agree that learning something new just because it's new is something we're forced to do much too often.
>>>
>>>Yes, ON ERROR can be made to work as it did in the the DBASE days. but you might want to look at again at TRY.. CATCH.
>>>It can do what what ON ERROR did and more and save you a lot of effort while doing it.
>>
>>I have been able to reduce the number of lines in a very critical routine from nearly 50 to just 10 lines, by using Try-catch.
>
>True, I had such cases as well, but OTOH try-catch will screw your debugging if it isn't localized enough. If an error occurs three levels down the call stack from the level where you have the try-catch, your aStack() won't show how did you get to the place where the error occurred. For it to be effective, it has to be rather local. Learned that the hard way, after many hours in the debugger.

Also true, I normally only have a few lines between Try and Catch.