--- In firebird-support@yahoogroups.com, "Steffen Heil" <lists@s...>
wrote:

> Hi
>
> First, there is nothing such as "embeded super server".
> There is super server, wich allowes multiple connections and runs

as

> standalone software.

sorry if we're using a wrong kind of terminology. It comes from not
being using/developing this database frequently.

> Then there is embeded server, wich is compiled into your

application and

> therefor only allows that application to access the database.
> Independent of the version you use, you CAN NEVER access the same

database

> file using multiple engines. Therefor embeded server MUST lock the

file.

>
> Don't even try to change the code to allow non-exclusive access,

it was done

> that way for some reason. Accessing the same database with two

engines will

> destory it. Definitly.
> One engine can never know what was changed by the other engine in

RAM

> already.

The application where the server has been embeded must run from CD-
ROM, so the database file will be *ALLWAYS* opened in the read-only
mode. So, what kind of problems can occure in this case? I would
say, no write - no destruction, or is it even wrong?

Is it possible to embed the classic server in any way? Even without
any coordinating processes?

>
> Use Super Server, NOT embeded for this.

It's impossible since the application must run from scratch without
installation.

>
> Regards,
> Steffen