I'm glad I'm not the only one who has been experiencing this problem. Here's what I've seen: I have two major customers. One uses a Windows NT network.
The other runs a combination of Windows NT/Novell 4.0.

In both cases I'm running VFP 6.0 (SP3) apps, and frequently update tables across the network. Both customers have their the tables located on Windows NT boxes.

I have NEVER seen this error on the NT-only customer's environment.
I see sporadic occurrences nearly every day on the NT/Novell customer's environment.

Is this somehow related to a disharmony between Novell 4.0/VFP 6 (SP3)?

FWIW, I raised this issue here a while back. I tried re-creating the indexes like one of you suggested, but this didn't help at all.