>George,
>
>>I checked, and they aren't *supposed* to be using anything else (Other than VFP7) to access the data in our system.
>
>Well it's possible the other thing isn't correctly writing the data, although it probably shouldn't be writing at all.
>
>Have you checked to make sure you aren't seeing this bit being flipped inside character fields too?
>
>>Why would this matter? Do these other products have a history of corrupting VFP tables? We thought it was too odd that seemingly random integer fields keep changing by EXACTLY 128.
>
>I've never heard of this, I'm just casting out some fodder for ideas.
>
>>BTW, we also saw currency fields unexpectedly changing. But those fields changed by trillions. It was asy to spot those errors. :)
>
>Network card failure? Memory problems client and file server? New machine on the network? Cabling problem? Harddisk problem?

I've seen similar errors on printers, when printing in character mode (old times), and suddenly all spaces would become = signs, numbers would convert to certain characters - from ASCII table one could simply judge which wire went (first often, then permanently) 1. A similar error may happen in any of the devices you mentioned. Now with printers it was easy - replace the cable. Here... good luck to originator of this thread.