Hi Steve,

>
> Client was a poor choice of words.

Very easy to do because thats what we call them, but it makes for a
confusing problem when you are not sure whether it is asking about a
customers server or a customers workstation.

I have a customer which is a small

> company with limited network resources. Therefore, the Firebird
> database server will also be used as a workstation.

OK, a quick warning, Firebird will attempt to use 100% of the CPU or
I/O capabilities for extended periods of the time if you give it a
nasty query to run. Also if that user does something nasty that uses
all the CPU or is very disk intensive, it will slow down other users
experience of the database.

If it is a small program with a small database, it probably wont
matter but if there are lots of users with serious database activity
there may be trouble. We never let a customer use anything other than
a dedicated machine as the server, but that is the nature of our
product. Yours may be less intensive.

You probably know that already but I would make it clear to your
customer that this is a consequence of their decision to use a
database server as a workstation.

Hense, on that

> machine, he'll be running the Firebird v1.5.2 Server and the Interbase
> v7.1 client.

From what I understand (correct me if I am wrong), the IB client is
simply a DLL.

Just don't tick the option in the FB installer to copy the library to
the sys32 folder and it should co-exist fine.

Because there is no interbase server installed on this machine,
Firebird should happily run on its normal 3050 port.

On other workstations, they'll run both the Firebird and

> Interbase client software.

That is fine, just copy the fbclient.dll into your application folder
(not a folder in the path such as system32), and when your application
launches it will use the FBClient in your folder.

The IB application should find the gds32.dll in its own folder.

Adam