At 09:39 PM 20/03/2005 +0100, you wrote:

>I'm having problems with ODBC and Clients with Firebird 1.5.
>I've followed all the steps from the Firebird-book from page 95 and so on as
>far as I could understand it. By the way: What does .local mean as file names
>on the client file list as file extension.
>The included pics has been removed.
>The Firebird server is on a Win2000 and the same is the database.
>There are no other processes using the database.
>
>I have to explain in words.
>
>I'm using Firebird/Interbase(r) driver MT ODBC 2.0 on System-DSN
>Datasource Name: TESTBASE02
>Driver: IscDbc

>Database: F:\TESTBASE02 as Placed on Server and Network Mapping

Can you describe exactly what you mean by "as Placed on Server and Network
Mapping"? Do you understand that you can *never* connect to a mapped drive
or server? That is, if the server does not have a physical drive or
partition that its host address directly as "drive F" then the server can
not connect to the database.

>Client: C:\WINNT\system32\GDS32.DLL
>Database Account: SYSDBA
>Password: masterkey
>Role: Nothing
>Character Set: NONE
>Options: None
>Extended identifier properties: quoted identifiers
>Dialect 3
>
>On test connection:
>Connection failed!
>File Database is used by another process.

Abandon the notion that a Firebird database is a Windows-style shared file
resource. Users (clients) request a *connection* to a database. Users
don't open a database *file*. It is the Firebird server that opens the
file (if it does not have it open already) and connects the client to the
database.

For Superserver, only the first client's connection request causes the
server to open the file. That first connection request will fail if the
file can't be opened, e.g. because the network has it mapped as a shared
resource, making it impossible for the server to get an exclusive lock on
the file. If the first connection request succeeds, then the server
program has an exclusive lock on the file.

./heLen