dancooperstock wrote:

>The need for these programs has me worried about whether Firebird is
>really rock-solid enough for me to use as the embedded DB in my
>application or not.
>
>

Firebird is very ligth so it's often used in OS that didn't offer any
kind of rock-solid solutions, like Windows 95 and 98.
Here you will find 99% of corruption cases. I think that the remaining
1% will be for many reasons, but not related to the Firebird engine by
itself.

The problem is, IMO, as simple as this: Firebird allows you to use it in
environemts that aren't just made to be used by a database engine.

>Under what sorts of circumstances do Firebird databases, and their
>backups, tend to get corrupted?
>
>

I have many years of experience using Firebird, and last week I saw my
first case of corruption: one of my clients press the reset button in a
middle of an operation that creates 800 invoices (usualy a operation
that takes 20 to 30 seconds to perform on that machine). Since this
client uses my aplication for one year now (small installation, 3
workstations, database server installed in one of the workstations) I
can imagine that this was really bad luck: the girl that pressed the
reset button told me that "I press reset a lot of times during the day -
the computer is on the floor, and my shoe is always pressing it".

Artur