At 09:52 PM 8/05/2004 +1000, you wrote:

> > 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.

That much is true: if port 3050 is already in use by one version of the
client (as it is, by default) then any "port override" by another client is
going to step on the established use of that port's service. But that's a
different matter: not one of a mismatched path string but of a port conflict.

A port conflict *does* cause that "busy" message, btw; as will a client
that is "calling" through a different port number for a gds_db service that
resolves to port 3050.

/heLen