I don't think ms office will intervene or there is any newer version of mdac later then 2.8. try use another format such as ip-number:alias_name
If you really suspect ms office is the problem, you may un-install office and test. Срд, 23 Мар 2011, Dave Albiston писал(а): > Hi Bart > > We are using server_name:alias_name. It work fine with the my Delphi > application so I think it can be ruled out as the cause of the problem. > > We are not using Office to connect. At the moment we are just trying to > set up the System dsn but the Test connection button always fails. > > I was under the impression that Office installs a different set of MDAC > components but that doesn't seem to be an issue. > > On 23/03/11 08:39, Bart Smissaert wrote: > > Have been using the Phoenix ODBC driver with various Office versions > > for years and no problem. > > Find that if there is any trouble it usually is a faulty connection string. > > What is the connection string you are using? > > > > RBS > > > > > > On Wed, Mar 23, 2011 at 8:25 AM, Dave Albiston > > <d...@cairngormsoftware.eu> wrote: > >> Hi Olaf > >> > >> My client is using 32 bit XP with Office 2003 and Office 2007. At the > >> moment we are just trying to set up the ODBC connection but the Test > >> Connection button always fails. > >> > >> A delphi application (using IBX components) is working so we know the > >> connection string and login credentials are correct and that the link > >> from the Firebird client to the server is OK. > >> > >> Is there some way to trace the cause of the failure with ODBC? > >> > >> On 22/03/11 14:43, Olaf Kluge wrote: > >>> > >>> Hello, > >>> > >>> yes, I have testet it with firebird odbc 2.0.0.150. I use two connections > >>> to > >>> firebird. All tables are connected to a system.dsn, stored procedures with > >>> an ADO-connection. > >>> > >>> What operating sytem you are using on your clients? 32 or 64bit? Can you > >>> connect with the ODBC-DSN (Test-Button). > >>> > >>> Olaf > >>> > >>> Thanks Olaf > >>> > >>> Can you confirm that you are using MS Office with the latest version > >>> (RC2) of the Firebird driver. > >>> > >>> I am looking for an explanation why the driver works perfectly on my > >>> machine > >>> but fails to connect on the client's desktop machines which have MS Office > >>> installed. It works on their server which does not have MS Office. The > >>> connection string and user details are all correct. > >>> > >>> On 22/03/11 11:43, Olaf Kluge wrote: > >>>> > >>>> Hello Dave, > >>>> > >>>> since Microsoft Windows XP, MDAC 2.8 is integrated. In Windows 2000 > >>>> you need to install the MDAC manually. > >>>> > >>>> We use Microsoft Office, especially Access to connect to firebird. I > >>>> have tested the gemini-odbc-driver, also the firebird-odbc-driver and > >>>> both works very well within all me known firebird-versions. > >>>> > >>>> You can use ODBC with all Applications using ODBC. With the > >>>> odbc-driver-manager you can test the connection to firebird. > >>>> > >>>> Best regards, Olaf > >>>> _____________________ > >>>> > >>>> > >>>> > >>>> My client is unsuccessful in connecting to the database using the ODBC > >>>> driver. I have tested the driver on all my machines and it works. > >>>> > >>>> Reading up on this, I discovered that MS Office (and other MS > >>>> products) install a different set of MDAC components. On the MS > >>>> knowledgebase, I discovered this: > >>>> > >>>> "With so many recent MDAC releases, applications have experienced > >>>> version incompatibility issues under certain circumstances." > >>>> > >>>> All my client's machines have MS Office installed, but I don't use it. > >>>> Is the Firebird driver compatable with MS Office? > >>> > >> > >> -- > >> > >> Dave Albiston > >> > >> Cairngorm Software Ltd > >> > >> Phone No. +44 (0)1383 729087 > >> Mobile No. +44 (0)7711 904030 > >> > >> ------------------------------------------------------------------------------ > >> Enable your software for Intel(R) Active Management Technology to meet the > >> growing manageability and security demands of your customers. Businesses > >> are taking advantage of Intel(R) vPro (TM) technology - will your software > >> be a part of the solution? Download the Intel(R) Manageability Checker > >> today! http://p.sf.net/sfu/intel-dev2devmar > >> _______________________________________________ > >> Firebird-odbc-devel mailing list > >> Firebird-odbc-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel > >> > > > > -- > > Dave Albiston > > Cairngorm Software Ltd > > Phone No. +44 (0)1383 729087 > Mobile No. +44 (0)7711 904030 > > ------------------------------------------------------------------------------ > Enable your software for Intel(R) Active Management Technology to meet the > growing manageability and security demands of your customers. Businesses > are taking advantage of Intel(R) vPro (TM) technology - will your software > be a part of the solution? Download the Intel(R) Manageability Checker > today! http://p.sf.net/sfu/intel-dev2devmar > _______________________________________________ > Firebird-odbc-devel mailing list > Firebird-odbc-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel -- regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Firebird-odbc-devel mailing list Firebird-odbc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
