> This is confusing and not true. It is fine to connect locally using
> localhost while a remote user connects using the server name. What will
> cause the "busy database error" is if different **path** strings are used
> and it's only possible on Windows. This is an example of different path
> strings:
>
> myserver:d:databases\mydb.fdb
> localhost:d:\databases\mydb.fdb
>
> These path strings are the same and OK for concurrent connection:
> myserver:d:\databases\mydb.fdb
> localhost:d:\databases\mydb.fdb
>
> /heLen

I stand corrected, it's not servername but the absence or presence of a port
to the connection string does make this connection problem.
servername:drive:\path
and
servername/3050:drive:\path
is not permitted. At least it doesn't work on my network.
Alan