Fabiano,

Take a look at the problems one-by-one:

> > -Changing metadata while database in use

This one should send a error message, but should not cause corruption. If it
does (I never had a corruption problem caused by this) it's really something
that should be fixed.

> > -Connecting to DB during restore

Probably the server must refuse connections when a restore is taken place.
Just do a restore using another name for the database, and after is finished
rename it.

> > -Connection strings mismatched

Not a problem in Firebird 1. Already fixed.

> > -Copying the database file(s) while in use

I don't know any way to prevent this to happen in the engine. Note that the
original Database is not corrupted, just the copy that was made using this
process.

> > -Deleting the current row in an UPDATE trigger

Ops. Never tried this. Can someone confirm this?

> > -Forced writes OFF

This is an operating system problem, not a engine problem. Firebird 1.5 as
another options to figth against this OS problem.

> > -Hardware glitches

No way to correct this at engine level.

> > -Mismatched client and server versions

No way to correct this at engine level.

> > -Server crashes

No way to correct this at engine level. :-)

> > -Too many transactions

Can anyone confirm if this could lead to corruption?

> > -Transporting database without transportable backup

This is not a corruption problem. This is just a user doing things in a
wrong way.

> I thought mixing local and remote connections on the same

database, but

> maybe can someone confirm that.

This should not create corruption. The engine is responsible for this.

Artur