>>I have been chasing this problem. Does not always repeat. But in the case of one customer every once in a while.
>>
>>I have the following code logged (simplified)
>>

>>cError = “Numeric overflow”   && created in code which I omit here
>>
>>STRTOFILE( TTOC(DATETIME()) + " FunctionName() Error: " + cError + " Value V_CURSOR.PRINT_ORD: " + 
>>IIF(TYPE("V_ CURSOR.PRINT_ORD")="N",ALLTRIM(STR(V_ CURSOR.PRINT_ORD)),"N/A") + CHR(13) + CHR(10), "Error.log", 1 )
>>

>>The strange thing is that when a user updates several records, the value of .PRINT_ORD is recorded in log as:
>>4100
>>4101
>>4102
>>…
>>on so on.
>>until 4117
>>
>>The value in .PRINT_ORD should not even be more than 100. The field itself, PRINT_ORD is Integer. So, even if the value was 4100, 4101, and so on, it should not be firing the Numeric Overflow error.
>>
>>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.