Packing is, in my experience of course, a better way to deal with damaged tables, although that wont necessarily take care of the source of the problem.

>After converting a VFP 3.0 form to VFP 7.0, I consistently (though not on >demand) crash on my tableupdate with a C0000005 both in development and in >production. I did notice one problem. I sometimes find records that are >not "deleted", should not be "deleted", but only appear when "set deleted >is off." Is this the sign of a damaged file? Reindexing usually solves >this problem but it's only a bandaid. I don't know what the source of the >problem is. TIA.