>Craig,
>
>I have rarely seen DBF corruption and I've always been able to trace it to:
>- Poorly designed applications
>- Hardware issues
>
>Agreed. When it happens, though, it can be a disaster. We've had one remote customer that kept seeing table corruption on their flaky network. Every single day. The cost to us was immense. The take-home lesson for us was that if a customer insisted on dbfs, they would be told in advance that if corruption occurs, the only available "fix" is to move to SQL Server.

That kind of corruption is simply unheard of ;
Unless you have client/company that uses *cat* as a doorbell (Monty Pyton), rents twiglight room of Adams house for an office, runs pirated DOS application on 286 machines, connects PCs via d-link 2pair network and powers them by problematic diesel inductor - without UPS! <vbg>

Kidding aside;
What a heck was going on in there, how come ?!?
Did you use buffering at all ?