firebird-odbc-devel — All about development of Firebird ODBC driver donated by IBPhoenix

Re: [Firebird-odbc-devel] MS Access #deleted with varchar UTF8 primary key

[Henner K. <Hen...@gm...>]

This is a problem using UTF-8. 

It's described here:

http://www.easysoft.com/support/kb/kb00929.html.


I patched the driver source to return a SQL_C_CHAR instead of SQL_C_WCHAR
and created a new MsVc90 project to generate an odbc driver named "Firebird
driver for MS Access".

This new driver works with MS Access 2003 and 2007 with Unicode databases.

Regards,
Henner

> -----Ursprüngliche Nachricht-----
> Von: Carsten Ulrich [mailto:Car...@mo...]
> Gesendet: Mittwoch, 18. Mai 2011 15:50
> An: fir...@li...
> Betreff: [Firebird-odbc-devel] MS Access #deleted with varchar UTF8
primary
> key
> 
> Hello,
> I want to open a table where the primary key is a varchar(50) Column with
> charset utf8. MS Access (2010) shows the Value #deleted for all columns.
If I
> change the charset of the primary key column to ISO8859_1 it works.
> 
> I use ODBC driver version 2.00.00.151
> 
> Thanks
> Carsten
> 
>
----------------------------------------------------------------------------
--
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its next-
> generation tools to help Windows* and Linux* C/C++ and Fortran developers
> boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel

Re: [Firebird-odbc-devel] Intermittant Crash on FIREBIRD ODBC DRIVER DLL (odbcfb32.dll)

[Alexander P. <ale...@gm...>]

On 19.05.2011 21:04, Vishal Batchu wrote:
>  Hi
>
> I don't know if anyone else experience a problem like mine, but the 
> two attached screen shots represent intermittant problems that i 
> continue to experience with our application using the Firebird Odbc 
> Driver.
>
> Here is my Setup
>
> Windows Xp sp 2
>
> Firebird v2.5.0.1.2xx.xx
>
> Firebird Odbc Driver v 2.0.0.151
>
> Development Language : Visual Basic 6
>
> Thank you.
>
> Vishal
>
The attached screen shots show that the driver version is 2.0.0.144, not 
2.0.0.151.

-- 
Alexander Potapchenko
Lead developer
LASP technology, http://www.lasptech.ru

Re: [Firebird-odbc-devel] Does Firebird ODBC driver support batches?

[Erich v. H. <eh...@ho...>]

Thank you Alexander.

Date: Fri, 20 May 2011 10:39:11 +0400
From: ale...@gm...

Firebird ODBC
      driver does not support explicit batches.

    

    

    -- 

       Alexander Potapchenko

        Lead developer

        LASP technology, http://www.lasptech.ru

      
    
  


------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Firebird-odbc-devel mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel 		 	   		  

Re: [Firebird-odbc-devel] Does Firebird ODBC driver support batches?

[Alexander P. <ale...@gm...>]

On 20.05.2011 4:32, Erich von Hauske wrote:
> Does Firebird ODBC driver support explicit batches? 
> http://msdn.microsoft.com/en-us/library/ms712553(v=vs.85).aspx 
> <http://msdn.microsoft.com/en-us/library/ms712553%28v=vs.85%29.aspx>
>
> I've been trying to execute a simple batch "SELECT * FROM 
> COUNTRY;SELECT * FROM COUNTRY" from Visual Fox Pro and it gives me an 
> error, I have tried with other tools and it gives me the same error:
>
> [ODBC Firebird Driver][Firebird]Dynamic SQL Error
> SQL error code = -104
> Token unknown - line 1, column 22
> SELECT
>
> SQLSTATE : HY000
>
> Native error code: -104
>
> Thank you for any help you can provide on this.
>
>
Firebird ODBC driver does not support explicit batches.


-- 
Alexander Potapchenko
Lead developer
LASP technology, http://www.lasptech.ru

[Firebird-odbc-devel] Does Firebird ODBC driver support batches?

[Erich v. H. <eh...@ho...>]

Does Firebird ODBC driver support explicit batches? http://msdn.microsoft.com/en-us/library/ms712553(v=vs.85).aspx
I've been trying to execute a simple batch "SELECT * FROM COUNTRY;SELECT * FROM COUNTRY" from Visual Fox Pro and it gives me an error, I have tried with other tools and it gives me the same error:
[ODBC Firebird Driver][Firebird]Dynamic SQL ErrorSQL error code = -104Token unknown - line 1, column 22SELECT
SQLSTATE : HY000
Native error code: -104
Thank you for any help you can provide on this. 		 	   		  

[Firebird-odbc-devel] MS Access #deleted with varchar UTF8 primary key

[Carsten U. <Car...@mo...>]

Hello,
I want to open a table where the primary key is a varchar(50) Column 
with charset utf8. MS Access (2010) shows the Value #deleted for all 
columns. If I change the charset of the primary key column to ISO8859_1 
it works.

I use ODBC driver version 2.00.00.151

Thanks
Carsten

[Firebird-odbc-devel] how to compile OdbcFb-Source-2.0.0151

[luxInteg <lux...@bt...>]

Greetings, 

 I  compiled  Firebird-2.5.0.26074-0 on a computer with these:

cpu -->    AMD64-2 cores
OS -->:   cblfs 64-bit linux, kernel-2.6.35 gcc-4.4.2 with ada/gnat, gfortran


I also  downloaded this  archive: "OdbcFb-Source-2.0.0151.tar.gz"   but  there 
does not seem to be any clear instructions how to compile  the sources.  
I even tried unpacking it  in the Firebird source tree to compile with the 
main Firebird building but this failed as  there is no autoconf configure.in 
script in  the generated  ODBC JDBC branch   to generate makefiles.  

I would thus  be grateful for advice on how to compile this package.

yours sincerely
luxInteg 

[Firebird-odbc-devel] stored procedure using default parameters

[Stefanie G. <sg...@ya...>]

________________________________
Hello!


I have problems using default parameters in stored procedures.
It is no problem to create a stored procedure like that:
execute procedure person_sel(persidx INTEGER, mode INTEGER DEFAULT 0)...

When I call it using odbc I have to set all parameters:
{Call PERSON_SEL(1,0)} 
otherwise({Call PERSON_SEL(1)}) I get the following error: count field incorrect

I use Firebird-ODBC-driver: 2.0.0.151 and Firebird 2.5.

Does anyone know a resolution to solve this problem?

Thanks in advance.

Best regards,
Stefanie Gocht

[Firebird-odbc-devel] FB ODBC for Servers 1.5.x on 64-Bit

[André K. C. <Kna...@be...>]

Hello!  Excuse me, please, if this is a stupid request; I am a bit out
of practice with installing ODBC.

For  legacy  reasons,  we  still need to support one installation of a
Firebird 1.5.x server.

While I am in general reluctant to have 64-Bit OS, now I have some CAD
workstations  where  the  advantages  outweigh the disadvantages, so I
need to deal with it.

Is the following installation scheme correct/good?
-  ODBC driver 2.0.0.151_x64
-  using an "fbclient.dll" from a 2.5. 64-Bit server installation
to access a 32-Bit 1.5.x FB server?

In a test install I managed to install the 1.0.2.0070 driver using the
"fbclient.dll"  from  1.5.6  server and could connect perfectly, but I
also  need  to  configer  DSNs using the ODBCAD32.exe in \System32 not
only that in \SysWoW62


Thanks in advance!
  

mit freundlichen Grüßen,

André Knappstein
EDV und Controlling
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
beta Eigenheim- und Grundstücksverwertungsgesellschaft mbH
Hafenweg 4
59192 Bergkamen-Rünthe

Telefon: +49 2389 9240 140
Telefax: +49 2389 9240 150
e-mail:  kna...@be...

Amtsgericht Hamm Nr. B 420
Geschäftsführer: Achim Krähling, Dirk Salewski und Matthias Steinhaus

USt-IDNr.: DE 125215402

---

Re: [Firebird-odbc-devel] Firebird Latest Odbc "SELECT TOP"

[Jorge A. B. <jor...@gm...>]

better choice: rows
not-so-good choice: first (Firebird supported but non standard compliant)

Regards

2011/4/15 Mig/ <mig...@gm...>

> We are porting to firebird some databases, some ODBC applications
> does not work because "SELECT TOP" does not work, there is a workaround?
> Since we are not able to change those application but only databases.
>
> Thanks
>
> --
> Regards,
> MIG
>
>
> ------------------------------------------------------------------------------
> 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
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>
>

Re: [Firebird-odbc-devel] [SPAM 4] Re: Driver still compatible with Interbase?

[Jorge A. B. <jor...@gm...>]

Agreed.

2011/4/12 Kjell Rilbe <kje...@da...>

> Den 2011-04-12 14:52 skrev Alexander Potapchenko såhär:
> > I think that ODBC driver 2.0 is compatible with Interbase, but I didn't
> > test the driver with IB.
> > The Firebird/InterBase(r) driver is the historical name and I think that
> > many application can use the such connection string:
> > strConn = "driver={Firebird/InterBase(r) driver}; Database=;
> > UID=SYSDBA;PWD=masterkey"
> > Therefore I think that to rename the driver is the bad idea as yet.
>
> While I sympathise with efforts for backwards compatibility, I find this
> very odd. If the driver is not being actively maintained for Interbase
> support and is not tested with IB, I think it is desinformation with
> such a name.
>
> I'd recommend a feature freeze for the driver with the old name and use
> a FB only name for all future versions.
>
> Kjell
> --
> --------------------------------------
> Kjell Rilbe
> DataDIA AB
> E-post: kj...@da...
> Telefon: 08-761 06 55
> Mobil: 0733-44 24 64
>
>
>
> ------------------------------------------------------------------------------
> Forrester Wave Report - Recovery time is now measured in hours and minutes
> not days. Key insights are discussed in the 2010 Forrester Wave Report as
> part of an in-depth evaluation of disaster recovery service providers.
> Forrester found the best-in-class provider in terms of services and vision.
> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>

Re: [Firebird-odbc-devel] Firebird Latest Odbc "SELECT TOP"

[Kjell R. <kje...@da...>]

Den 2011-04-15 09:23 skrev Alexander Potapchenko såhär:
> On 15.04.2011 11:11, Mig/ wrote:
>> We are porting to firebird some databases, some ODBC applications
>> does not work because "SELECT TOP" does not work, there is a workaround?
>> Since we are not able to change those application but only databases.
>>
>> Thanks
>>
>> --
>> Regards,
>> MIG
>>
>
> "SELECT TOP" is not standard sql. That is a typical Microsoft only feature.
> Always, when you migrate from one system to another you have to make
> sure, that your software is only using SQL commands, that are defined in
> the SQL standard.

If I'm not mistaken the SQL standard now includes the rows clause:

select *
from table
rows 1 to 20

Not sure about odbc etc and I don't think SQL Server supports rows, but 
FB 2.5 does.

Kjell
-- 
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kj...@da...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64

Re: [Firebird-odbc-devel] Firebird Latest Odbc "SELECT TOP"

[Alexander P. <ale...@gm...>]

On 15.04.2011 11:11, Mig/ wrote:
> We are porting to firebird some databases, some ODBC applications
> does not work because "SELECT TOP" does not work, there is a workaround?
> Since we are not able to change those application but only databases.
>
> Thanks
>
> -- 
> Regards,
> MIG
>

"SELECT TOP" is not standard sql. That is a typical Microsoft only feature.
Always, when you migrate from one system to another you have to make 
sure, that your software is only using SQL commands, that are defined in 
the SQL standard.


Regards,
Alexander
-- 
Alexander Potapchenko
Lead developer
LASP technology, http://www.lasptech.ru

[Firebird-odbc-devel] Firebird Latest Odbc "SELECT TOP"

[Mig/ <mig...@gm...>]

We are porting to firebird some databases, some ODBC applications
does not work because "SELECT TOP" does not work, there is a workaround?
Since we are not able to change those application but only databases.

Thanks

-- 
Regards,
MIG

Re: [Firebird-odbc-devel] [SPAM 4] Re: Driver still compatible with Interbase?

[Alexander P. <ale...@gm...>]

On 14.04.2011 22:20, Jorge Andres Brugger wrote:
> Alexander, there is some kind of roadmap or concrete ideas about 
> future development of odbc driver?
Bugs fixing in 2.0.1. The is no roadmap for 2.1 now.

-- 
Alexander Potapchenko
Lead developer
LASP technology, http://www.lasptech.ru

Re: [Firebird-odbc-devel] [SPAM 4] Re: Driver still compatible with Interbase?

[Jorge A. B. <jor...@gm...>]

Alexander, there is some kind of roadmap or concrete ideas about future
development of odbc driver?

Regards

2011/4/12 Alexander Potapchenko <ale...@gm...>

> On 12.04.2011 17:03, Kjell Rilbe wrote:
>
> > I'd recommend a feature freeze for the driver with the old name and use
> > a FB only name for all future versions.
> >
> > Kjell
> It is possible in new version 2.1... but this version will be not in the
> near future.
>
> --
> Alexander Potapchenko
> Lead developer
> LASP technology, http://www.lasptech.ru
>
>
> ------------------------------------------------------------------------------
> Forrester Wave Report - Recovery time is now measured in hours and minutes
> not days. Key insights are discussed in the 2010 Forrester Wave Report as
> part of an in-depth evaluation of disaster recovery service providers.
> Forrester found the best-in-class provider in terms of services and vision.
> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>

Re: [Firebird-odbc-devel] [SPAM 4] Re: Driver still compatible with Interbase?

[Alexander P. <ale...@gm...>]

On 12.04.2011 17:03, Kjell Rilbe wrote:

> I'd recommend a feature freeze for the driver with the old name and use
> a FB only name for all future versions.
>
> Kjell
It is possible in new version 2.1... but this version will be not in the 
near future.

-- 
Alexander Potapchenko
Lead developer
LASP technology, http://www.lasptech.ru

Re: [Firebird-odbc-devel] [SPAM 4] Re: Driver still compatible with Interbase?

[Kjell R. <kje...@da...>]

Den 2011-04-12 14:52 skrev Alexander Potapchenko såhär:
> I think that ODBC driver 2.0 is compatible with Interbase, but I didn't
> test the driver with IB.
> The Firebird/InterBase(r) driver is the historical name and I think that
> many application can use the such connection string:
> strConn = "driver={Firebird/InterBase(r) driver}; Database=;
> UID=SYSDBA;PWD=masterkey"
> Therefore I think that to rename the driver is the bad idea as yet.

While I sympathise with efforts for backwards compatibility, I find this 
very odd. If the driver is not being actively maintained for Interbase 
support and is not tested with IB, I think it is desinformation with 
such a name.

I'd recommend a feature freeze for the driver with the old name and use 
a FB only name for all future versions.

Kjell
-- 
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kj...@da...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64

Re: [Firebird-odbc-devel] Driver still compatible with Interbase?

[Alexander P. <ale...@gm...>]

On 12.04.2011 15:54, Jorge Andrés Brugger wrote:
> ODBC driver 2.0 is still compatible with Interbase? or should better be
> renamed to "Firebird ODBC driver"?
>
> Regards!
>
I think that ODBC driver 2.0 is compatible with Interbase, but I didn't 
test the driver with IB.
The Firebird/InterBase(r) driver is the historical name and I think that 
many application can use the such connection string:
strConn = "driver={Firebird/InterBase(r) driver}; Database=; 
UID=SYSDBA;PWD=masterkey"
Therefore I think that to rename the driver is the bad idea as yet.

Regards,
Alexander
-- 
Alexander Potapchenko
Lead developer
LASP technology, http://www.lasptech.ru

[Firebird-odbc-devel] Driver still compatible with Interbase?

[Jorge A. B. <li...@da...>]

ODBC driver 2.0 is still compatible with Interbase? or should better be 
renamed to "Firebird ODBC driver"?

Regards!

-- 
Jorge Andrés Brugger
Informática
DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia
Comodoro Rivadavia, Chubut, Argentina
Teléfono (0297) 446-4444 int. 103
Correo electrónico: jbr...@da...
Website: www.dasu.com.ar

[Firebird-odbc-devel] Win7 asks for UN-PW FireBird in reports

[Venus S. O. <ven...@gm...>]

Hi all

I use FireBird as a backend. Report Manager as the reporting engine. I pass the Connection String to the FireBird database to Report Manager reports which includes the user name and password. The reports will then run very well without a problem.

Under Windows 7, this same starts asking the user for a Under Name and Password, once provided the report will run properly again. This is a PITA and troubles the application to work seamlessly.

This was observed when installed using Firebird_ODBC_1.2.0.69-Win32.exe setup.

Please advise

Thanks and regards
Bhavbhuti


-- 


Thanking you.

Yours Faithfully,
For Venus Software Operations
----
Bhavbhuti Nathwani
___________________________________________
Softwares for Indian Businesses at: http://www.venussoftop.com

ven...@gm...
ven...@ma...
___________________________________________

Please note: We reserve complete rights for policy changes in the future and the same will be applicable immediately as and when made.  Attachments may get corrupted before reaching you, in such a situation please let us know and we will resend you the same at the earliest.  We do not take any responsibility for data loss of any type and kind.  Data safety remains the sole the responsibility of the users of our softwares.
___________________________________________

Internet email confidentiality:

This message may contain information that may be privileged or confidential.  If you are not the addressee nor are you responsible for the delivery of the message to the addressee indicated in this email, then you may not copy or deliver this email to anyone and you should notify the sender by reply email and then destroy this message.

Please reply email immediately to this message with REMOVE in the subject, if you or your employer do not consent to email of this kind.

Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by my company.

Re: [Firebird-odbc-devel] MS Office compatability

[Bart S. <bar...@gm...>]

Could you run this code from VBA in Excel or Word after setting a
reference to ADO (2.8)?
Alter the Dbname and PWD and UID.
Does it connect? It tests the ODBC driver without using a DSN.

Sub TestODBC()

  Dim oADOConn As ADODB.Connection
  Dim strConn As String

  Set oADOConn = New ADODB.Connection

  strConn = "Driver={Firebird/InterBase(r) driver};" & _
            "Dbname=localhost:C:\DB\s6.fdb;" & _
            "PWD=password;" & _
            "UID=username;"

  MsgBox oADOConn.State  'will be 0

  oADOConn.Open strConn

  MsgBox oADOConn.State  'should be 1

End Sub


RBS


On Wed, Mar 23, 2011 at 2:00 PM, Dave Albiston
<da...@ca...> wrote:
> I can connect from the workstations without ODBC. So Firebird client is
> installed correctly, the connection string and user details are correct
> and there is no firewall blocking the port.
>
> But still we cannot connect when setting up the dsn. There is something
> peculiar to these machines, but how do I find out what it is?
>
> This thread really has the wrong subject now. MS Office is obviously not
> a factor.
>
> On 23/03/11 12:10, Bart Smissaert wrote:
>> Can you connect in Excel via ADO, ODBC and a DSN-less connection
>> string with some VBA code?
>>
>> RBS
>>
>>
>> On Wed, Mar 23, 2011 at 11:04 AM, Dave Albiston
>> <da...@ca...>  wrote:
>>> Hi there
>>>
>>> The configuration settings are correct. We proved it by setting up a dsn
>>> on the actual database server with the same settings and it worked.
>>>
>>> It does not work on the workstations. But the same settings are used in
>>> a delphi application running on the workstations which connects without
>>> a problem.
>>>
>>> Judging by the feedback on this thread, it sounds like MS Office is not
>>> an issue.
>>>
>>> Is there a way to investigate why I get the
>>>
>>> "Open database 'server_name:alias_name' failed"
>>>
>>> Is there a trace log of some kind? There appears to be something
>>> peculiar about my client's PCs. The driver works on everything else I
>>> have tested it on.
>>>
>>>
>>> On 23/03/11 10:10, Marco Held wrote:
>>>> Hello Dave,
>>>>
>>>> when pressing the Test button, do you get any error message? Please send us
>>>> all your settings you filled in to the configuration of the ODBC DSN.
>>>>
>>>> Regards, Marco
>>>>
>>>>
>>>>
>>>>
>>>> Marco Held
>>>>
>>>> phone: +49 271 77202 27
>>>> e-mail:  mh...@de...
>>>>
>>>>
>>>>
>>>> demig Prozessautomatisierung GmbH – www.demig.de – in...@de...
>>>> Haardtstraße 40 – D-57076 Siegen – Tel. +49 271 77202 0  –  Fax +49 271
>>>> 77202 92
>>>> Registergericht Siegen HRB 2819 – Geschäftsführer Joachim Herbst, Winfried
>>>> Held
>>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: Dave Albiston [mailto:da...@ca...]
>>>> Gesendet: Mittwoch, 23. März 2011 10:43
>>>> An: Bart Smissaert
>>>> Cc: fir...@li...
>>>> Betreff: Re: [Firebird-odbc-devel] MS Office compatability
>>>>
>>>> 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
>>>>> <da...@ca...>     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
>>>>>> Fir...@li...
>>>>>> 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
>>> Fir...@li...
>>> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> 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
>> Fir...@li...
>> 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
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>

Re: [Firebird-odbc-devel] MS Office compatability

[Dave A. <da...@ca...>]

I can connect from the workstations without ODBC. So Firebird client is 
installed correctly, the connection string and user details are correct 
and there is no firewall blocking the port.

But still we cannot connect when setting up the dsn. There is something 
peculiar to these machines, but how do I find out what it is?

This thread really has the wrong subject now. MS Office is obviously not 
a factor.

On 23/03/11 12:10, Bart Smissaert wrote:
> Can you connect in Excel via ADO, ODBC and a DSN-less connection
> string with some VBA code?
>
> RBS
>
>
> On Wed, Mar 23, 2011 at 11:04 AM, Dave Albiston
> <da...@ca...>  wrote:
>> Hi there
>>
>> The configuration settings are correct. We proved it by setting up a dsn
>> on the actual database server with the same settings and it worked.
>>
>> It does not work on the workstations. But the same settings are used in
>> a delphi application running on the workstations which connects without
>> a problem.
>>
>> Judging by the feedback on this thread, it sounds like MS Office is not
>> an issue.
>>
>> Is there a way to investigate why I get the
>>
>> "Open database 'server_name:alias_name' failed"
>>
>> Is there a trace log of some kind? There appears to be something
>> peculiar about my client's PCs. The driver works on everything else I
>> have tested it on.
>>
>>
>> On 23/03/11 10:10, Marco Held wrote:
>>> Hello Dave,
>>>
>>> when pressing the Test button, do you get any error message? Please send us
>>> all your settings you filled in to the configuration of the ODBC DSN.
>>>
>>> Regards, Marco
>>>
>>>
>>>
>>>
>>> Marco Held
>>>
>>> phone: +49 271 77202 27
>>> e-mail:  mh...@de...
>>>
>>>
>>>
>>> demig Prozessautomatisierung GmbH – www.demig.de – in...@de...
>>> Haardtstraße 40 – D-57076 Siegen – Tel. +49 271 77202 0  –  Fax +49 271
>>> 77202 92
>>> Registergericht Siegen HRB 2819 – Geschäftsführer Joachim Herbst, Winfried
>>> Held
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Dave Albiston [mailto:da...@ca...]
>>> Gesendet: Mittwoch, 23. März 2011 10:43
>>> An: Bart Smissaert
>>> Cc: fir...@li...
>>> Betreff: Re: [Firebird-odbc-devel] MS Office compatability
>>>
>>> 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
>>>> <da...@ca...>     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
>>>>> Fir...@li...
>>>>> 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
>> Fir...@li...
>> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>>
>
> ------------------------------------------------------------------------------
> 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
> Fir...@li...
> 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

Re: [Firebird-odbc-devel] MS Office compatability

[Bart S. <bar...@gm...>]

Can you connect in Excel via ADO, ODBC and a DSN-less connection
string with some VBA code?

RBS


On Wed, Mar 23, 2011 at 11:04 AM, Dave Albiston
<da...@ca...> wrote:
> Hi there
>
> The configuration settings are correct. We proved it by setting up a dsn
> on the actual database server with the same settings and it worked.
>
> It does not work on the workstations. But the same settings are used in
> a delphi application running on the workstations which connects without
> a problem.
>
> Judging by the feedback on this thread, it sounds like MS Office is not
> an issue.
>
> Is there a way to investigate why I get the
>
> "Open database 'server_name:alias_name' failed"
>
> Is there a trace log of some kind? There appears to be something
> peculiar about my client's PCs. The driver works on everything else I
> have tested it on.
>
>
> On 23/03/11 10:10, Marco Held wrote:
>> Hello Dave,
>>
>> when pressing the Test button, do you get any error message? Please send us
>> all your settings you filled in to the configuration of the ODBC DSN.
>>
>> Regards, Marco
>>
>>
>>
>>
>> Marco Held
>>
>> phone: +49 271 77202 27
>> e-mail:  mh...@de...
>>
>>
>>
>> demig Prozessautomatisierung GmbH – www.demig.de – in...@de...
>> Haardtstraße 40 – D-57076 Siegen – Tel. +49 271 77202 0  –  Fax +49 271
>> 77202 92
>> Registergericht Siegen HRB 2819 – Geschäftsführer Joachim Herbst, Winfried
>> Held
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Dave Albiston [mailto:da...@ca...]
>> Gesendet: Mittwoch, 23. März 2011 10:43
>> An: Bart Smissaert
>> Cc: fir...@li...
>> Betreff: Re: [Firebird-odbc-devel] MS Office compatability
>>
>> 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
>>> <da...@ca...>   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
>>>> Fir...@li...
>>>> 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
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>

Re: [Firebird-odbc-devel] MS Office compatability

[Bart S. <bar...@gm...>]

Can you connect in Excel via ADO, ODBC and a DSN-less connection
string with some VBA code?

RBS


On Wed, Mar 23, 2011 at 11:04 AM, Dave Albiston
<da...@ca...> wrote:
> Hi there
>
> The configuration settings are correct. We proved it by setting up a dsn
> on the actual database server with the same settings and it worked.
>
> It does not work on the workstations. But the same settings are used in
> a delphi application running on the workstations which connects without
> a problem.
>
> Judging by the feedback on this thread, it sounds like MS Office is not
> an issue.
>
> Is there a way to investigate why I get the
>
> "Open database 'server_name:alias_name' failed"
>
> Is there a trace log of some kind? There appears to be something
> peculiar about my client's PCs. The driver works on everything else I
> have tested it on.
>
>
> On 23/03/11 10:10, Marco Held wrote:
>> Hello Dave,
>>
>> when pressing the Test button, do you get any error message? Please send us
>> all your settings you filled in to the configuration of the ODBC DSN.
>>
>> Regards, Marco
>>
>>
>>
>>
>> Marco Held
>>
>> phone: +49 271 77202 27
>> e-mail:  mh...@de...
>>
>>
>>
>> demig Prozessautomatisierung GmbH – www.demig.de – in...@de...
>> Haardtstraße 40 – D-57076 Siegen – Tel. +49 271 77202 0  –  Fax +49 271
>> 77202 92
>> Registergericht Siegen HRB 2819 – Geschäftsführer Joachim Herbst, Winfried
>> Held
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Dave Albiston [mailto:da...@ca...]
>> Gesendet: Mittwoch, 23. März 2011 10:43
>> An: Bart Smissaert
>> Cc: fir...@li...
>> Betreff: Re: [Firebird-odbc-devel] MS Office compatability
>>
>> 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
>>> <da...@ca...>   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
>>>> Fir...@li...
>>>> 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
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>