>>>>Could anyone suggest a possible problem/solution?
>>>
>>>Are you sure that the error was caused by writing a value into this alias?
>>
>>I put a line:
>>
>>cPoint = "Point where the error occurred. The value of .PRINT_ORD is " + str( V_CURSOR.PRINT_ORD)
>>
>>right before the REPLACE command.
>>Then the code goes to the CATCH to oError.
>>So, I presume that the error is caused by the REPLACE.
>>I can't think where else the error would be caused.
>
>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"
What am I missing?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
