I've seen the same problems, but they typically result in mismatched headers or corrupted indexes, not a file full of chr(0). This problem is a little different, but I'll look into that with these occurrences.

Thanks for your input.

>Normally table corruption is caused by bad network connections or people who don't close down the programs properly. In our contracts we require that the users have one UPS per PC plus one for each server. We haven't experienced corrupted tables in years since we included this requirement in our contracts. No UPS means no guarantee.
>
>>I am having 2 or 3 customers a month come to me with tables that have become corrupted. When I look at the tables, the entire contents of the file have been replaced with chr(0). Most of our customers are running in a networked environment with multiple machines accessing the tables. Most commonly these machines are all running Windows XP sp3. Does anyone know what causes this or how to prevent it?