>The operation of our main app involves the distribution of free FoxPro tables across our WAN. For reasons yet unknown, the data sometimes suffers corruption. Randomly, character field data will be replaced by chr(0).
>
>Q1: Does anyone have experience with this problem?

Yes I have encouner a similar problem. IMO it's a result of network/hardware problems but it's very hard to prove it to the network guys. The only way to fix damage is to restore the table from a backup.

>
>We have recently encountered a corrupted table which FoxPro would happily open but unfortunately would not handle properly. It appears that we can't reliably detect this problem using FoxPro code.
>
>Q2: What would be the best means of handling this kind of damage?


Usually Foxpro just blows up on that kind of damaged table. I don't think there is a way to detect it progrmmaticaly besides opening dbf file by low level i/o function and check for chr(0) in the records area.

>
>Thanks