I didn't encounter such error on regular basis and when I did it was memo corruption. There's no point to continue in such case until table is repaired.
The problem lies outside of VFP. Why copy is performed outside VFP in the first place? If you do it using COPY TO command, you wouldn't have the problem.

>Okay, one final question to you and others: Is this kind of exception explicitly handled by your exception handler? If so, what type of handling can be advised here?