>>Ah, if you already have the oError object, why don't you pass that object to your error handler, and write out all the properties that may be relevant. There's more info in there than just the error message.
>
>How do you "pass the object to the error handler"?
>My error handler is Try/Catch with Catch to oError. And the oError.message says "Numeric overflow. Data Lost"

Ah okay, not calling any general routine to handle errors but rather doing it on the spot. Stylistic difference, of the „where does the code go“ kind. Irrelevant. The error handler routine, when one is written, should accept the exception object as a parameter, that's what I meant.

>What am I missing?

Other properties of oError - it can give you line number, source line, perhaps the name of the thing where it happened (field, property - not each time) and a few other things. Check it out, class exception, its PEMs.