[Firebird-odbc-devel] Problems with PC clients

[Maury Markowitz]

I have an extensive set of reporting tools in Excel that run against the Firebird database in Fishbowl Inventory using a DSN-less ODBC connection string. The string is...

Const cnn = "ODBC;Driver={Firebird/InterBase(r) driver};Client=E:\Fishbowl\odbc\fbclient32.dll;Datasource=192.168.3.200;Database=E:\Fishbowl\database\data\AS SOLAR.FDB;UID=gone;PWD=fishing;"

As you can see, the server has been installed on the E drive, and this sheet works great on that machine.

However, when I move to other machines in the office, I get generic errors - a problem in VBA's reporting of ODBC problems.

So first question... can I point to a client DLL on another machine?

Assuming I could not, I changed the Client= to the path to the DLL on the local machine, but that didn't help.

Any suggestions on how to test this? VBA basically hides all real information in these cases and simply returns "1004"

[Dimitry Sibiryakov]

Post by Maury Markowitz
I changed the Client= to the path to the DLL on the local machine

Install fbclient.dll to default accessible path using instclient and remove "Client"
part from connection string at all.
Every client machine must have firebird client properly installed (not just copied).

[Maury Markowitz]

Post by Dimitry Sibiryakov
Install fbclient.dll to default accessible path using instclient and remove "Client"
part from connection string at all.

What is the "default accessible path" in this case?

Fishbowl ships with the 64-bit dll only, installed in it's own Program Files path. Running the installer and pointing it to that dll with the Client line works fine. This is true even on the client machines.

It is only the 32-bit version that appears to be having problems. That was manually installed in the same directory as the 64-bit version. Is this not correct?

[Dimitry Sibiryakov]

Post by Maury Markowitz
What is the "default accessible path" in this case?

RTFM: http://msdn.microsoft.com/en-us/library/ms886736.aspx

[Maury Markowitz]

Not the problem then.

Post by Dimitry Sibiryakov

Post by Maury Markowitz
What is the "default accessible path" in this case?

RTFM: http://msdn.microsoft.com/en-us/library/ms886736.aspx

[Steffen Heil (Mailinglisten)]

Hi

I don't think Excel is running on Windows CE.
But the cause of the problem might be right.
Just make sure to check the correct msdn article.
NOT the references one.

Regards,
Steffen

-----Ursprüngliche Nachricht-----
Gesendet: Donnerstag, 29. November 2012 18:16
Betreff: Re: [Firebird-odbc-devel] Problems with PC clients

Post by Maury Markowitz
What is the "default accessible path" in this case?

RTFM: http://msdn.microsoft.com/en-us/library/ms886736.aspx
--
WBR, SD.

----------------------------------------------------------------------------
--

VERIFY Test and improve your parallel project with help from experts and
peers. http://goparallel.sourceforge.net
_______________________________________________
Firebird-odbc-devel mailing list
https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel

[Dimitry Sibiryakov]

Post by Steffen Heil (Mailinglisten)
Just make sure to check the correct msdn article.
NOT the references one.

Huh? Do you know any difference in LoadLibrary() between Windows editions?

[Steffen Heil (Mailinglisten)]

Hi

Post by Dimitry Sibiryakov
Huh? Do you know any difference in LoadLibrary() between Windows editions?

Not between "usual" Windows editions, but CE is somewhat special.
See:

http://msdn.microsoft.com/en-us/library/windows/desktop/ms684175%28v=vs.85%2
9.aspx

The function itself does the same in a very similar manner.
However that article includes information about search folders and such.
This is no necessarily equal to CE.

Regards,
Steffen

[Jorge Andrés Brugger]

Use the odbc driver installer
(http://www.firebirdsql.org/en/odbc-driver/) on the other machine. Also
remove the client part from the connection string.

Post by Maury Markowitz
I have an extensive set of reporting tools in Excel that run against the Firebird database in Fishbowl Inventory using a DSN-less ODBC connection string. The string is...
Const cnn = "ODBC;Driver={Firebird/InterBase(r) driver};Client=E:\Fishbowl\odbc\fbclient32.dll;Datasource=192.168.3.200;Database=E:\Fishbowl\database\data\AS SOLAR.FDB;UID=gone;PWD=fishing;"
As you can see, the server has been installed on the E drive, and this sheet works great on that machine.
However, when I move to other machines in the office, I get generic errors - a problem in VBA's reporting of ODBC problems.
So first question... can I point to a client DLL on another machine?
Assuming I could not, I changed the Client= to the path to the DLL on the local machine, but that didn't help.
Any suggestions on how to test this? VBA basically hides all real information in these cases and simply returns "1004"
------------------------------------------------------------------------------
VERIFY Test and improve your parallel project with help from experts
and peers. http://goparallel.sourceforge.net
_______________________________________________
Firebird-odbc-devel mailing list
https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel

[Maury Markowitz]

Post by Jorge Andrés Brugger
Use the odbc driver installer
(http://www.firebirdsql.org/en/odbc-driver/) on the other machine.

I ran Firebird_ODBC_2.0.0.150_x64 on all of the machines in question.

Post by Jorge Andrés Brugger
Also
remove the client part from the connection string.

I did. That causes it to fail on all machines, including the previously working server.