>Thanks guys.
>
>I wasn't asking about how to resolve the issue; that was taken care of using the steps I mentioned (essentially recalling the record in question then re-deleting it). My puzzlement has to do with how this scenario can exist. I am not a FoxBASE internals expert, but would assume the deletion mark is a bit setting. That being the case I'd think FoxBASE would see a record only as being DELETED or NOT, but not BOTH as it was in this case.
>
>Thanks anyway.

Actually Deleted record are marked with an asterisk in the first column of the row. If the table structure has a total length of 100 character, then the actual record length would be 101. I once, long ago, encountered a data corruption problem similar to yours. The problem turned out to be a Non-asterisk character was placed in the Delete column. Fox, at time, saw the non-white space character and thought it as deleted, where other times it would see it as non-space character and thought it as not deleted. After tracking down the offending character and replacing it with a space character the problem went away.