Corrupt data can certainly cause a C5, but based on posts here and other forums, I would suspect the Foxuser file before the actual data.

>Because I got C0000005 errors on a read operation involving a data table and records with corrupted memo field pointers, it's highly probable that you could have problems going the other way, such as a INSERT INTO.
>
>But think about the operation that is occurring. It would add a record to the table, update the CDX if necessary, and FPT file if there is one. All these files have to be healthy AND the user must have the priviledges to write/modify the files and the files must not be marked read-only.
>
>If it can't complete the write operation anywhere along the line, then it would get an error from the OS and if Foxpro couldn't handle the error, it would die and pass the error through.
>
>Kind of like what is happening, perhaps?