Subject | RE: [firebird-support] MS Access ODBC to Firebird |
---|---|
Author | Michael Möhle |
Post date | 2012-01-18T08:57:56Z |
Installation Order:
- Firebird Server (only client)
- ODBC Driver 32 Bit
- ODBC Manager is in Control Panel -> 32 Bit Control Panel
The ODBC driver depends only on the Bits of the application not on the
Bits of the operating neither on the Bits of the Firebird Server
32 Bit APP -> 32 Bit ODBC Driver -> 32/63 Bit Operating
System/Firebird Server
64 Bit APP -> 64 Bit ODBC Driver -> 32/63 Bit Operating
System/Firebird Server
And the ODBC Driver depends on the gds32.dll/fbclient.dll for that you need
the Installation Package of the Firebird Server, corresponding to
the bitness of the ODBC driver. If you install the Server there is a
dropdown box where you can choose client only install.
Michael
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Peter M
Sent: Tuesday, January 17, 2012 12:36 PM
To: firebird-support@yahoogroups.com
Subject: [firebird-support] MS Access ODBC to Firebird
Hello,
A cli e nt recently had their application changed to run firebird rather
than paradox . It worked fine, with MS Access apps connecting to provide
data feeds from firebird. It is version 1.5 I am told.
Then it was moved to a windows server 2008.
I can no longer get MS Access to connect to the the firebird tables.
The problem seems to be in the ODBC setup, I can't run an effective test
that sets up and stores the user name and password.
The connection to the MS Access dbs is via remote desktop as well, in case
that matters.
My questions are these.
What ODBC driver should I install on the server, and should it be under
remote desktop session or directly form eth console.?
Firebird is version 1.5 I am told, what ODBC driver is best.?
Should it be 32 bit or 64 bit driver?
Is there any other clues you may be bale to offer to get this connected?
there eseems to be an issue in how the path to the data source is
described, it workd sometimes as " localhost: p:\ dir1\dir2zapp.xyz", and
sometimes without the localhost bit, which i think relates to it being a
remote connection.
Any help greatly appreciated.
Best
Peter Marshall
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
- Firebird Server (only client)
- ODBC Driver 32 Bit
- ODBC Manager is in Control Panel -> 32 Bit Control Panel
The ODBC driver depends only on the Bits of the application not on the
Bits of the operating neither on the Bits of the Firebird Server
32 Bit APP -> 32 Bit ODBC Driver -> 32/63 Bit Operating
System/Firebird Server
64 Bit APP -> 64 Bit ODBC Driver -> 32/63 Bit Operating
System/Firebird Server
And the ODBC Driver depends on the gds32.dll/fbclient.dll for that you need
the Installation Package of the Firebird Server, corresponding to
the bitness of the ODBC driver. If you install the Server there is a
dropdown box where you can choose client only install.
Michael
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Peter M
Sent: Tuesday, January 17, 2012 12:36 PM
To: firebird-support@yahoogroups.com
Subject: [firebird-support] MS Access ODBC to Firebird
Hello,
A cli e nt recently had their application changed to run firebird rather
than paradox . It worked fine, with MS Access apps connecting to provide
data feeds from firebird. It is version 1.5 I am told.
Then it was moved to a windows server 2008.
I can no longer get MS Access to connect to the the firebird tables.
The problem seems to be in the ODBC setup, I can't run an effective test
that sets up and stores the user name and password.
The connection to the MS Access dbs is via remote desktop as well, in case
that matters.
My questions are these.
What ODBC driver should I install on the server, and should it be under
remote desktop session or directly form eth console.?
Firebird is version 1.5 I am told, what ODBC driver is best.?
Should it be 32 bit or 64 bit driver?
Is there any other clues you may be bale to offer to get this connected?
there eseems to be an issue in how the path to the data source is
described, it workd sometimes as " localhost: p:\ dir1\dir2zapp.xyz", and
sometimes without the localhost bit, which i think relates to it being a
remote connection.
Any help greatly appreciated.
Best
Peter Marshall
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]