Thanks for all your suggestions, everyone.

As frequently happens, the fault lies in ourselves .... I found an old piece of code in the form for this which, in effect, replace all records in the table, not just the one record being updated, each time that a record was updated.

No wonder I saw the error I was getting.



>It depends on SET TABLEVALIDATE setting and default value 3 would generate an error.
>
>>>I have gotten sporadic reports where a user makes modifications to a few of the records in the table (which he can then see in the grid), closes out of the form, and when he returns later, finds that the modifications he's made have disappeared.
>>
>>One possible cause of this is a corrupted DBF header. If the record count stored in the header is incorrect, you won't get an error opening the table and even TABLEUPDATE() will return .T., leading you to believe that everything is fine, but table updates, especially adding records, often fail. Try packing the table to see if that helps.