>Hi,
>Buffering (any types) doesn't prevent table corruption. There are a lot of possible causes of corruption, network, memory, HDD, display driver problem and etc. You could get more info by visiting fox.wikis.com and search topic with keyword "corruption".
>
>You could try to turn off HDD Write cache, use FLUSH FORCE after transaction (only available in VFP9) to minimize the chance.
>
>HTH


It does not fully prevents it, but it can lower it to completely acceptable level. Point is that it directly minimises time of actual writing to tables
on discs when corruption actually occurs due to known reasons.

I achieved almost corruption free operation with buffering 5 and use of transactions, by keeping all tables buffered (5) at all times and then saving all table changes (or nothing) in one go at certain events.
In fact I implemented one advice/example from VFP5 developers manual
some 10 years ago and made it into generic datasaving class, and saw corruption twice ever since. (Index file burst, no actual data ever)

I am very happy with it :)