Subject Re: Cannot connect to a local database
Author phil_hhn
--- In, Helen Borrie <helebor@t...>
> At 11:49 PM 11/08/2004 +0000, you wrote:
> >WinXP SP1,
> >Firebird 1.5:
> >fbserver.exe (WI-V1.5.0.4306)
> >fbguard.exe (WI-V1.5.0.4306)
> >IBExpert 2004 (2004.4.1.1)
> It's also important to find out whether you have the correct client
> library. For most Delphi-built tools (like IBExpert and IB_SQL) it
> to be gds32.dll, located in the system directory and having the same
> number as the server.
in windows\system32, gds32.dll: WI-V6.3.0.4306

> For Fb 1.5 you'll need to read the docs about how to convert
> into a compatible gds32.dll for IBExpert.
So does that gds32.dll above seem right, or should I go thru the step
you suggest for converting fbclient.dll?

> >I cannot create a new database on their PC using IBExpert (I get the
> >same error).
> >I've tried connecting to their database from my IBExpert (register new
> >database) but again get the same error.
> Sounds like a bad or missing client.
I've uninstalled FB and IBExpert then reinstalled it all, so do you
know what could be missing?

> >, but seems I have to specify the database file also
> Client applications connect to databases. They do this via the
server. If
> you were able to just "connect to the server", what would you expect
to see/do?
I thought I'd be able to serve up (eg) c:\Database0 on port 3050 as a
default (and optionally c:\temp\Database1 on port 3051,
c:\temp\Database2 on port 3052, etc.), so a client just connects to an
IP and a pre-determined port for a particular database.

> >(is this going to work when it's on their machine?).
> Provided you have configured you app to connect to the correct
> path for the database file, yes.
Yep... We may have one install with a server on XP and MAC & linux
clients connecting to it, and another setup with the server on linux
and windows & MAC clients connecting to it. This is why it's nice for
a client to be able to simply connect on a known port (and server
machine name discovered via DNS) to get the database service.
By having to specify the database file on the client end, the clients
need to know what type of file system the DB is on (to construct the
correct path), and this can change from one linux server to the next,
depending on how particular a linux admin is...
And if the OS of the database platform were to change (ignore the IP
because it could still be the same or the client finds it via same
hostname) then all the clients need to be updated if the file system
requires the database path to be constructed differently.

> Aliasing helps a lot here. Have the app
> connect to an alias and configure the path in aliases.conf. When
> then all you need to do is edit aliases.conf on the deployed server.
Ummm... is that platform-specific ( page 16350.html
suggests its for win32 only :-( )

> Wrong. The *server* is listening on the IP and port combination.
The IP
> is the network address of the server hardware. The port is the
socket that
> is listening for a connection request. Both are server-level. The
path in
> the connection string directs the server to the location of the
> file. The !!! correct !!! client library connects the client app to
> appropriate database. (There may be many databases on a single server).
That's what I was expecting, hence my query re. ports, hoping that I
could tie one database to one port (may also be easier for the server,
knowing it can have a separate process for each port, and not have to
multiplex requests to multiple databases on the same port :-) ).

> For a local connection you need to use the localhost IP address. Check
> that the %system%\drivers\etc\hosts file has the entry
> localhost
That's all fine....

> >Where can I find IB_SQL?
> Download at (button top RH side of main page).

Thanks, will get IB_SQL and give it a crack