> That's not the reason. If one server tries to write data to a

database

> that's controlled by another server, or even another CPU (no server
> installed) corruption is inevitable. And it's not the kind of

corruption

> you can fix by using gifx to tidy up orphaned pieces.

You can stop there, I totally agree (but that wasn't how I read his
question). If another server has firebird installed, and you have
firebird installed and you also set your firebird to control that
database, then you are really playing russian roulette without
leaving any blanks.

The situation that has been asked of me before (and the one I thought
to be behind his question) is where they have a file server that is
backed up daily and an application server where they want to install
firebird. This is still a very bad idea. If that is what you are
after, then put gbak in a scheduled job that runs before the backup
of the server.

In whatever case, install and use firebird only on the machine that
you want to hold your fdb file, don't install it anywhere else, use
fbclient.dll to connect to it from another workstation.

Adam.