Subject | Re: [IBO] Connection with tcp_ip protocol |
---|---|
Author | hypmarie23 |
Post date | 2007-03-23T16:27:07Z |
--- In IBObjects@yahoogroups.com, "Woody" <woody-tmw@...> wrote:
It was because of GDS32.DLL in SYSTEM32. At the installation, I had
renamed FBBCLIENT.DLL in GDS32.DLL and so I had GDS32.DLL (same as
FBCLIENT.DLL) and FBCLIENT.DLL.
Now I have only FDBCLIENT.DLL and it works with TCP_IP AND LOCAL.
What is the correct way to deal with these dlls if I want to use
Interbase also ?
>files. I
> From: "hypmarie23" <mariematignon@...>
> > --- In IBObjects@yahoogroups.com, Stefan Heymann <lists@> wrote:
> >>
> >> > Check the value of the FIREBIRD variable.
> >>
> >> > Try pinging localhost.
> >>
> >> > Try telnet-ing to it.
> >>
> >> + Try using an all-lowercase Alias (in aliases.conf and in your
> >> connection properties)
> > It doesn't change any thing.
>
> This problems sounds almost like you have two different alias.conf
> normally use the embedded FB client in the program directory so Ican switch
> to local easy if testing on a machine without FB installed orrunning. That
> means I have an alias.conf file in the program directory whenrunning
> locally and one in the Firebird directory when running over TCPIP.Could
> this be a problem for you as well?I just solved my problem :
>
> Woody (TMW)
>
It was because of GDS32.DLL in SYSTEM32. At the installation, I had
renamed FBBCLIENT.DLL in GDS32.DLL and so I had GDS32.DLL (same as
FBCLIENT.DLL) and FBCLIENT.DLL.
Now I have only FDBCLIENT.DLL and it works with TCP_IP AND LOCAL.
What is the correct way to deal with these dlls if I want to use
Interbase also ?