>>....Seems one of his men in the warehouse turned off the server right in the >middle of the busiest part of the day.
>
>Are VFP files the only files that break when a server is turned off? Sounds like there was some weakness in the implementation. Few shops place servers in areas where someone is likely to do this. They're either locked in a cabinet or personel understand the DO NOT TOUCH policy.
>
>I don't think that an enduser turning off a server during a transaction and the resulting data corruption, should be blamed on VFP's DBF engine. Rather, the problem seems to be 1) The end user that turned off the server, and (2)the administrator responsible for leaving the server in a unsecure area. I don't think VFP had anything to do with it. I don't think bad luck had anything to do with it. Somebody was on a quality assurance holiday - and thats all that happened:-).

Terry;

You can add to the list - the ISO decided to have a blackout in your power zone, etc. Access tables break without power interuption. I have seen SQL Server break due to improperly turning off a server. If you do things correctly you can rebuild SQL Server - then it is not a problem. I have never broken Oracle or Sybase but have no concept how robust they are. They may be like SQL Server - they come with the tools to rebuild a database - in case needed - if you know what you are doing.

Tom