Every time I have seen this error, reindexing the table has cleared it up.

Whether it was really FoxPro's fault or not that the index got messed up, who knows and who cares? Just rebuild the indexes and let the users get back to work.

Mike