The version of VFP makes no difference. VFP tables are corruptable w/little effort. They can be corrupted by machine failures, disk failures, power failures, network difficulties, etc.

If you are using VFP tables then a good reliable UPS is absolutely required on any machine that hosts the tables and any machine that accesses the tables. This is by far the cheapest and least complicated route for that situation. A good UPS is made by APC or TrippLite or several other major manufacturers. Don't by a cheapie. Don't buy an off-brand. Do it right and it will save time and money. Look for On-Line UPSs rather than standby UPSs.

Test the UPSs regularly - every 6 months or so. Batteries die over time. UPS circuitry can die over time.

Other than that, move to SQL Server where the database is not touched by anything other than the SQL Server itself, and where SQL Server maintains transaction logs that it can use to repair its databases. You should absolutely have a good UPS on a SQL Server as well, but you do not need one on the clients in this case.


>A programmer here at work is having trouble with losing data when there is a power failure. Since some of our stores have lost data that was apparently saved, he does tests that involve turning power off, to simulate a power failure.
>
>The sample program does a FLUSH, and also closes tables and database (which I consider overkill, but just in case...). We already disabled write cache on the hard disks. But still, data gets lost when power is turned off.
>
>Is there anything else we have to watch out for?
>
>Would a later version of VFP help?
>
>TIA,
>
>Hilmar.