At 09:33 AM 1/03/2006, Adam wrote:

>The c:\Program Files tree only allows administrators to write (by
>default). I am not sure what happens differently when using a local
>connection, it is possibly as simple as the log or locking mechanism
>can not be written to disk, or maybe the client tries to directly
>write something to the fdb file (although I would expect that only the
>server process is allowed to do this which should be under
>localsystem). Maybe someone more knowledgable can shed some light.
>
>In any case, if you don't use the hostname, then only one user can
>access it at a time. I must say that we never use local connection for
>this reason (exception of embedded engine which we are trialing but
>that is different, it lives in a folder to which the user has write
>permissions).

Adam, aren't you getting confused here with Fb Embedded? An IPServer
connection is not a blocking connection. Certainly, it's not
recommended to try to do multiple concurrent connections through
IPServer because of memory space issues...but IPServer does emulate a
network transport and doesn't preclude multiple connections.

The reason FbEmbedded is a blocking client is that it embeds the
Superserver, and the first connection to Superserver opens the
database file with an exclusive read/write lock.

I suspect that Rony's problem here was that he is running Classic,
which simply cannot use IPServer at all, i.e. it must use either
TCP/IP or Named Pipes.

./heLen