Thanks Larry, but what you suggest is beyond the scope of our app. Although we operate a WAN, this particular app is designed to use free tables only, located on local and LAN drives.

Further to my original message, it has been observed that when the chr(0) damage affects large blocks of records, a
simple copy of the table appears to rid it of almost all the errors.

Q: Does this suggest a physical problem?

Strange indeed.