>
>I wouldn't expect any corruption, but can imagine at least disk errors
>if power fails at the wrong moment. But you're right, I know a bit of
>SQL and may answer some of those questions, but have no knowledge of
>running a server and should leave this for those of you having that
>knowledge.
>
>Set

We have a situation where we have about 400 sites countrywide, each using
IB 6 as the production DB, in small 2 or 3 machine networks. We have users
who can be politely described as being "computer illiterate" and
"technology - hostile". The favourite and most widely used problem solving
technique is the "three finger salute" (Pressing ctrl - alt - delete to
restart the machine). If it doesn't work quickly enough, our users just
physically switch the machine off and on again at the power point.

We had problems initially with corrupt databases. However, after Ann posted
a long post about db corruption and how it happens, we turned "forced
writes" on - in fact, the application checks (every time it is started) for
this, and if forced writes are not on, will set them on.

We are running all sorts of Microsoft OS's, from Windows 98 OSR 2 to
Windows XP and 2000. Since we made sure that forced writes were on, we have
not had any problems with either db corruption or with commits / rollbacks.

Regards

Tim


[Non-text portions of this message have been removed]