Subject | Re: Embedded FB1.5 Doesn't Like "localhost". |
---|---|
Author | barfingdog_2004 |
Post date | 2004-04-18T18:33:33Z |
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
I'm not familiar with the method Windows uses to
select which DLL file to use. I thought the folder
where the executable resides was the first place
Windows looks for DLLs.
None of the directories in my PATH variable have
a copy of fdclient.dll or gds32.dll. This includes
D:\WINNT\system32.
I don't know what the Firebird installer set up
when I installed the client/server package. This is
a development system, and I tried to select an install
that wouldn't impact a system that has many tasks not
related to Firebird. It runs as a service, it starts
when I hit the button in the Firebird control panel
app, not at startup.
I need to push forward with some development while
we figure out what I'm doing wrong. I've restarted
the Firebird service so I can cut some code.
I re-asserted the host name and database name for
a client/server relationship and compiled.
But I decided to try one more thing. I left the
embedded fbclient.dll in the debug directory. I also
have its twin, gds32.dll, in the same directory.
Both are 1481 KB in size. That's the size of the
embedded DLL. There is no client only fbclient.dll
in the executable's directory.
My program worked, apparently it connected to the
server. Is that to be expected when using the embedded's
DLL? With the big embedded server DLL in the executable's
directory, should the app still depend on, or use, the
Firebird server?
Thanks
Larry
wrote:
> At 08:14 PM 16/04/2004 +0000, you wrote:have a
>
>
> >*** IBPP::Exception inside Database::Connect ***
> >
> >IBPP Message : isc_attach_database failed
> >
> >SQL Message : -904
> >Unsuccessful execution caused by an unavailable resource..
> >
> >Engine Code : 335544375
> >Engine Message :
> >unavailable database
> >
> > ----------
> >
> >What am I doing wrong?
> >
> >I've changed nothing else in the code that works
> >for a client-server relationship.
> You see, if your application can't find the database, one has to wonder
> whether it is actually even *loading* the embedded server. If you
> copy of fbclient.dll or gds32.dll in the system path (e.g. in thesystem32
> directory) it's well possible that your application is finding itinstead,
> and looking for a running server to connect to.Thanks Hellen:
I'm not familiar with the method Windows uses to
select which DLL file to use. I thought the folder
where the executable resides was the first place
Windows looks for DLLs.
None of the directories in my PATH variable have
a copy of fdclient.dll or gds32.dll. This includes
D:\WINNT\system32.
I don't know what the Firebird installer set up
when I installed the client/server package. This is
a development system, and I tried to select an install
that wouldn't impact a system that has many tasks not
related to Firebird. It runs as a service, it starts
when I hit the button in the Firebird control panel
app, not at startup.
I need to push forward with some development while
we figure out what I'm doing wrong. I've restarted
the Firebird service so I can cut some code.
I re-asserted the host name and database name for
a client/server relationship and compiled.
But I decided to try one more thing. I left the
embedded fbclient.dll in the debug directory. I also
have its twin, gds32.dll, in the same directory.
Both are 1481 KB in size. That's the size of the
embedded DLL. There is no client only fbclient.dll
in the executable's directory.
My program worked, apparently it connected to the
server. Is that to be expected when using the embedded's
DLL? With the big embedded server DLL in the executable's
directory, should the app still depend on, or use, the
Firebird server?
Thanks
Larry