Subject AW: [Firebird-Architect] None local database file
Author Klement Guenther - Munich-MR
> The historical reason for the restriction
(no databasefile access over network)
> was that it was impossible to
> prevent or detect two servers (or classic clients) from going at the
> database from different nodes, which is an absolutely certain way to
> trash a database beyond recovery. On networks that could reliably

Jim, you are right
things can sometimes get complicated.

But there are simpler solutions I'm thinking of.
On networks the hole database file will be locked and no other server is allowed to open the database
not even readonly.

The point of view is that of an single user application treating the database file more as a document file than a multi user database. This is specially try when using classic server.

Guenther beeing three weeks off now