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

> > Is it OK to have both these dlls in system32? My app uses the legacy
> > gds32.dll but the FB utils like gbak will use fbclient.dll. I'm
> > getting an error on gbak that says another process has the database
> > open. I have tried several very simple versions of the gbak .bat job
> > on the same PC where FB is running (and the app using localhost).
> > Thanks.
> >
>
>You have to use identical connection strings.
>So on the server you have to have
>servername:drive:\path
>and on the remote PCs you also have to have
>servername:drive:\path
>if a remote machine uses servename:drive\path
>then you can't connect on the server (locally) using localhost

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

>Alan
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>