| Subject | Re: [firebird-support] ODBC Connectivity |
|---|---|
| Author | Helen Borrie |
| Post date | 2012-12-09T18:40:34Z |
At 04:27 a.m. 10/12/2012, Hugh Thomson wrote:
On the client side you have application->driver->fbclient.dll. The application talks to the driver and fbclient.dll talks to the server. The bitness of the driver should be the same as the application and the fbclient. Install the driver on the client machine and make sure the path is valid for remote access, e.g., doggie:D:\databases\mydb.fdb. Substitute the machine name of the host machine for "doggie" here and "D" must be a physical partition on the host, not a remote share.
For further ODBC-related questions please use the firebird-odbc-devel list, where there are other warm bodies who were ODBC newbies once. It helps to provide the actual connection attributes you use as something like 'path:\....\*.fdb' says nothing useful for troubleshooting.
When posting to the lists, please avoid using your verbose company sig. We're happy just to know your name :-)
^ heLen ^
>Hello Support,The ODBC driver is a client layer.
>
>Me, Newbie.
>
>We are struggling to get the above to work. Tried all available versions of the drivers (both 32 and 64) and installed onto Win 2008R2 Std 64-Bit servers (virtual) but the Firebird ODBC Setup (from the Control Panel/Admin applet) keeps failing with the error message "Open database 'path:\....\*.fdb' failed". Even moved the DB to the local drive with no success.
On the client side you have application->driver->fbclient.dll. The application talks to the driver and fbclient.dll talks to the server. The bitness of the driver should be the same as the application and the fbclient. Install the driver on the client machine and make sure the path is valid for remote access, e.g., doggie:D:\databases\mydb.fdb. Substitute the machine name of the host machine for "doggie" here and "D" must be a physical partition on the host, not a remote share.
For further ODBC-related questions please use the firebird-odbc-devel list, where there are other warm bodies who were ODBC newbies once. It helps to provide the actual connection attributes you use as something like 'path:\....\*.fdb' says nothing useful for troubleshooting.
When posting to the lists, please avoid using your verbose company sig. We're happy just to know your name :-)
^ heLen ^