Hello,

>>> My application is loaded on a server so that it doesn't have to be
>>> deployed to each workstation. Is there a way to avoid installing
>>> the Firebird client on each workstation?

>> No; because the client provides the network connection layer as
>> well as the data transport layer. When it is invoked by the
>> application, it waves its arms and says "Hey, network, I'm node X,
>> listening for gds_db on port 3050, who's a server?" So that is a
>> node-to-node communication, not just software-to-software.

> Thanks Helen. Just to confirm, even if the client machines only have
> a shortcut to the application, which is housed on the server, I
> still need the Firebird client installed on the client machines,
> correct?

No, not necessarily, as long as the app can find the client library.
I once did exactly the same installation as you describe above, on
a Windows network. Application on the server, workstations had
shortcuts. In order for this to work the client library (gds32.dll or
fbclient.dll) must be copied to the same directory as the application
- one of the places where Windows looks for a DLL is the app dir.

Of course this means that application *and* client library are loaded
over the network every time.

> Is there anyplace that I can get a list of the files installed by
> the Firebird "client only" installation?

The "barest" client is just the DLL I think. Not sure about the
messages file. But I generally choose "client with tools", which also
installs gbak, isql etc. in the Firebird bin subdir.


Greetings,
Paul Vinkenoog