>Thanks - the problem occurred after we stopped getting the read errors due to the mapping problem. I can see where the problem I am seeing happened a few times before, but only once since changing from using the mapped drive.
>
>It is really strange - I can open the table, set the order to the order number, then seek the number that had the problem, and it takes me to a record that should have the order number in it, but the order number field is blank. Does anyone know what sequence FoxPro updates tables/indexes? I always assumed that it added the record to the table then updated the index. This looks like it somehow updated the index to reflect what is supposed to be in the record, but didn't get the data in the record....

My understanding is the same as yours, the table should get updated before the index. If it isn't, that implies something interfering with normal file system operations.

One thing that does that is antivirus programs. Maybe you could test with real-time scanning temporarily disabled on all machines that access or host the data, or exclude the VFP data and temp file folder(s) from real-time scanning.

Any other process that hooks the file system? On Win10 File History can do so if configured, also 3rd party "real-time" backup products that do similar things.

It might be worth looking at the System and Application Event Logs on the machine hosting the data.

At first I thought that if you had any new hardware - computers or network switchgear - it might be worth looking at that. But on second thought if they were flaky you would likely see more random errors; what you're describing seems consistent in its weirdness ;)