>Basicly, you'll have to scan whole table and look for unusual characters in the fields.

Heavy stuff.

When in your experience does the shifting of bytes corruption happen?

During usage or after a dbf is closed but is not properly written by the machines/net cards?

>
>>Thanks Sergey for responding.
>>
>>>There's no reliable way in FoxPro to detect table or index corruption.
>>
>>Any unreliable way you can suggest.
>>
>>I was thinking maybe I can get a snapshot of some bytes in a structured manner when I close a table (assuming that the dbf is in okay condition). Then when the dbf is reused I can compare the snapshots, if they match the dbf is okay, if not there is corruption.
>>
>>But, but does this corruption happen after a close?
>>
>>Clients can manage corruption, I can't duplicate it.
>>
>>Especially the shifting of data type, does this happen in use or after as the net card could not write the dbf?