I have seen that error when the length of the numeric field is not long enough when you are inserting data into a cursor or table.

John

>I am using VFP6. During an import of a transaction file, I receive the error message "Numeric overflow, data will be lost" - no number just the message. It did not trigger my error handling program.
>I discovered the offending numeric field and fixed the problem in my update code.
>Replace TranLog.Mark_up with iif(uTranlog.Mark_up>1000,1,uTranlog.Mark_up)
>
>Currently there is only this one field that does this and I don't know why just yet. As providence would have it, the value for this field can only go to about 10. The other fields can be in the millions.
>
>I would hate to replace every numeric field with something like that.
>
>The user report an error (not this one) on the selected record but it was created anyway and exported.
>
>It appears to be an isolated incident but it caused the import action to stop.
>
> Is there a better way? Is there a way to capture the error before hand so I can log it into my error table and then deal with later?
>
>Glen