--- In firebird-support@yahoogroups.com, "Adam" <s3057043@y...> wrote:

> This is a stark contrast to Paradox / DBase etc, where a problem
> during a write might leave a record in an invalid state.

I don't know about Paradox too good, but dBL/dBase fully supports
transaction-logic with commit() and rollback(). Best you combine it
with Try/Endtry/Finally-statements.
This protects against power-loss as well as Firebird does.
If a 'dBase-Programmer' does not use such security-functions...
well... just too bad for him and his customers.

> There are only three ways I can see that an application developer
> could accidentally stuff a database.
>
> 1. Inside a UDF
> 2. Running in embedded mode
> 3. Turning Forced Writes Off

How about copying an *.fdb while transactions are running and later
just copying it back?
How about making a restore while users are connected and active?
I am sure that there are more possibilities :)
Of course, they are quite stupid in a certain sense. But only the same
stupidity or carelessness can break a dBase-database as easy. At least
this is what I saw in ALL cases of a broken dBase-database; just
carelessness.

If dBase would not be stuck on/with the BDE, I would most likely NOT
convert to Firebird. But it is, and so I am converting... and Firebird
is really great.

ciao,
André