>Thanks George! I have been chasing this problem for several months. Each time I approach it I get a slightly different perspective. As of today, I am going to be comparing the calculated size of a file with the actual size using FSIZE and if there is a difference I am going to stop the user in his tracks and force running SDT's REPAIR function. At the same time, each time the program is started FoxFix is running in the background. I apparently can't stop the problem from occuring but this at least will limit the damage. Day before yesterday I looked at a clients data where roughly half the entries in 1 table were just missing. This apparently had been going on for some time and they just weren't paying attention, but if I get many more situations like that I will be looking for another line of work.

Calvin,

If the problem is chronic (and it appears to be), I think it would be far better to try and determine what the cause is. There are some things, such as latency over the network, which would require external adjustments to things such as network cache size. Others, such as the network stability, may require hardware upgrades or upgrades to the network OS (service packs, etc.).

What I'm saying isn't that you're taking the wrong approach. You're doing absolutely the right thing by trying to eliminate or reduce the problem on your side of the fence. However, if the problem persists, additional measures may be required.