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

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

[Olaf K. <ola...@sa...>]

Hello,

if this works on the server, there is no guarantee that it works on the
client. The server itself takes the database. It is strange, that it works
with your Delphi-application. But these uses not the odbc-dsn.

We don't know your dsn-settings, can it be a problem with the dns-service?
Use you a dns-name for your server or set you the ip-address in your dsn?
Does a firewall block this connection or the port? You can test the
accessibility of the server-name or ip-address by a ping.

You need also to install firebird on your client-pc. (minimal client
installation)

Olaf
___________________


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

[Marco H. <m....@de...>]

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

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

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

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

[Olaf K. <ola...@sa...>]

Hello,

if the dsn-connection-test fails, the office-applications cannot connect.

For example the firebird odbc settings:

Dsn: DSNNAME
Description: what you want
Database: SERVERNAME:LW:Path (f.e. server:d:\interbase\datenbank.fdb)
Client: C:\Programme\Firebird\Firebird_2_5\bin\fbclient.dll
Database Account: SYSDBA
Password: masterkey
Character Set: ISO8859_1
Dialect: 3

What error message do you get?

Olaf

_________________________

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 
> > <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

--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3

------------------------------------------------------------------------------
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

[Marco H. <m....@de...>]

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

[bill l. <cbi...@gm...>]

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
> > <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

-- 
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3

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

[bill l. <bbi...@gm...>]

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
> > <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

-- 
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3

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

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

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

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

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

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
>

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

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

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

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

[Olaf K. <ola...@sa...>]

If you are using the odbc-direct-function in your office-application, since
2007 this function was removed.

Till later than.

Olaf


_____________________
Thank Olaf

I'll check with my client. They are 4 hours ahead of me so I will have to
wait for a response until tomorrow. I am pretty sure it is XP 32 bit. 
I am not sure which version of Office they have - probably 2007.

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

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

[Olaf K. <ola...@sa...>]

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

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

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

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

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

[Olaf K. <ola...@sa...>]

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

[Firebird-odbc-devel] MS Office compatability

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

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

[Firebird-odbc-devel] Remote connection to the database with ODBC driver fails

[Mansoor, Y. <Yas...@du...>]

Hi, 

I can connect to the database with an ODBC connection on the server
using a remote connection string: server_name:Database_alias. There is a
problem connecting to the database from a remote machine using the same
connection string and credentials. The Test connection button always
fails.

>From the remote machine a Delphi application can connect to the database
using the same connection string and credentials (via the GDS32.dll).

OS = Windows Server 2003 R2 standard edition Service Pack 2
Hardware = Intel Xeon (Virtual Machine)

Any suggestions about possible cause?

Yasar Mansoor
Solution Analyst
Information Technology
Dubai Petroleum 
Mobile: +971 50 242 6422
Office: +971 4 301 2374
Fax: +971 4 301 2200
e-Mail: yas...@du... 


This message is intended only for the use of the individual(s) to which it is addressed and may contain information that is privileged and confidential. If you are not the intended recipient, you are hereby notified that you have received this transmission in error; any review, dissemination, distribution or copying of this transmission is strictly prohibited. If you have received this communication in error, please notify us immediately by reply e-mail or via the company switchboard on +9714 343-2222, and delete this message and all of its attachments. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Dubai Petroleum Establishment(DPE). While every effort has been taken to ensure this e-mail is virus free the recipient should always check all e-mails and attachments for the presence of viruses and worms. DPE does not accept legal responsibility for the contents of this e-mail as it has been transmitted over a public network. All information and attachments remain the property of DPE.
 

Re: [Firebird-odbc-devel] OdbcFb 2.0 raises error when delete empty set

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

On 09.03.2011 10:31, Ivan Ravin wrote:
>
> Is it possible to make this behavior tunable in datasource options 
> (make indicator "ODBC driver 1.x compatible" or something else, like 
> transaction, dialect or identifier options)?
>
> Some programs support Firebird like outdated server and don't want 
> support new features and accept warnings like errors. I got this 
> exception in CA Data Modeler 
> (http://erwin.com/products/detail/ca_erwin_data_modeler_standard_edition/):
>
> delete from DCT$Objects where Object_Name='AH_EXPORT_FACT'
>
> [ODBC Firebird Driver]No rows updated or deleted
>
> Execution Failed!
>
>
Hi Ivan,
For information: this code is added here - 
http://tracker.firebirdsql.org/browse/ODBC-13.
If CA Data Modeler can't work with warnings, then I think you need 
special build...

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

Re: [Firebird-odbc-devel] OdbcFb 2.0 raises error when delete empty set

[Ivan R. <iv...@ni...>]

Is it possible to make this behavior tunable in datasource options (make
indicator "ODBC driver 1.x compatible" or something else, like transaction,
dialect or identifier options)?

Some programs support Firebird like outdated server and don't want support
new features and accept warnings like errors. I got this exception in CA
Data Modeler
(http://erwin.com/products/detail/ca_erwin_data_modeler_standard_edition/):

 

delete from DCT$Objects where Object_Name='AH_EXPORT_FACT'

 

[ODBC Firebird Driver]No rows updated or deleted

Execution Failed!

 

 

 

  _____  

From: Alexander Potapchenko [mailto:ale...@gm...] 
Sent: Thursday, January 27, 2011 1:22 PM
To: fir...@li...
Subject: Re: [Firebird-odbc-devel] OdbcFb 2.0 raises error when delete empty
set

 

On 27.01.2011 11:25, Ivan Ravin wrote: 

No rows updated or deleted

I think that SQLExecute returns SQL_SUCCESS_WITH_INFO (warning) instead of
SQL_ERROR. 
I think it is correctly.


Regards,
Alexander

-- 

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

Re: [Firebird-odbc-devel] ODBC standard version support

[Steve B. <sbo...@gm...>]

Done.  ODBC-115.


Alexander Potapchenko wrote:
> On 07.03.2011 17:50, Alexander Potapchenko wrote:
>   
>> On 07.03.2011 16:43, Stephen Boyd wrote:
>>     
>>> Can anyone tell me what version of the ODBC standard the Firebird 
>>> ODBC driver supports?  I am running into problems trying to use 
>>> Firebird ODBC (2.0.150) with Open Office 3.3, which claims to only 
>>> support version 3 of ODBC.
>>>
>>>       
>> I have tried to use Open Office 3.3 and I have problem with select 
>> from table - "Fetch type out of range". It is a problem in Open Office.
>> You can look at SQLFetchScroll function description - 
>> http://msdn.microsoft.com/en-us/library/ms714682%28v=vs.85%29.aspx. 
>> The value of the SQL_ATTR_CURSOR_TYPE statement attribute was 
>> SQL_CURSOR_FORWARD_ONLY, and the value of argument FetchOrientation 
>> was not SQL_FETCH_NEXT.
>> Open Office 3.3 uses SQL_CURSOR_FORWARD_ONLY and SQL_FETCH_FIRST 
>> simultaneously.
>>
>>     
> After the additional analysis of the driver source code I have found 
> wrong and implicit type conversion of the cursor (conversion to type 
> SQL_CURSOR_FORWARD_ONLY). Please create issue in the bug tracker - 
> http://tracker.firebirdsql.org/browse/ODBC about your problems with the 
> driver in the Open Office.
>
> Regards,
> Alexander
>
>   

Re: [Firebird-odbc-devel] ODBC standard version support

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

On 07.03.2011 17:50, Alexander Potapchenko wrote:
> On 07.03.2011 16:43, Stephen Boyd wrote:
>> Can anyone tell me what version of the ODBC standard the Firebird 
>> ODBC driver supports?  I am running into problems trying to use 
>> Firebird ODBC (2.0.150) with Open Office 3.3, which claims to only 
>> support version 3 of ODBC.
>>
> I have tried to use Open Office 3.3 and I have problem with select 
> from table - "Fetch type out of range". It is a problem in Open Office.
> You can look at SQLFetchScroll function description - 
> http://msdn.microsoft.com/en-us/library/ms714682%28v=vs.85%29.aspx. 
> The value of the SQL_ATTR_CURSOR_TYPE statement attribute was 
> SQL_CURSOR_FORWARD_ONLY, and the value of argument FetchOrientation 
> was not SQL_FETCH_NEXT.
> Open Office 3.3 uses SQL_CURSOR_FORWARD_ONLY and SQL_FETCH_FIRST 
> simultaneously.
>
After the additional analysis of the driver source code I have found 
wrong and implicit type conversion of the cursor (conversion to type 
SQL_CURSOR_FORWARD_ONLY). Please create issue in the bug tracker - 
http://tracker.firebirdsql.org/browse/ODBC about your problems with the 
driver in the Open Office.

Regards,
Alexander

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

Re: [Firebird-odbc-devel] ODBC standard version support

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

On 07.03.2011 16:43, Stephen Boyd wrote:
> Can anyone tell me what version of the ODBC standard the Firebird ODBC driver supports?  I am running into problems trying to use Firebird ODBC (2.0.150) with Open Office 3.3, which claims to only support version 3 of ODBC.
>
Firebird ODBC driver supports ODBC standard 3.
I have tried to use Open Office 3.3 and I have problem with select from 
table - "Fetch type out of range". It is a problem in Open Office.
You can look at SQLFetchScroll function description - 
http://msdn.microsoft.com/en-us/library/ms714682%28v=vs.85%29.aspx. The 
value of the SQL_ATTR_CURSOR_TYPE statement attribute was 
SQL_CURSOR_FORWARD_ONLY, and the value of argument FetchOrientation was 
not SQL_FETCH_NEXT.
Open Office 3.3 uses SQL_CURSOR_FORWARD_ONLY and SQL_FETCH_FIRST 
simultaneously.
It is necessary to wait for the new version of Open Office.

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

[Firebird-odbc-devel] ODBC standard version support

[Stephen B. <sbo...@gm...>]

Can anyone tell me what version of the ODBC standard the Firebird ODBC driver supports?  I am running into problems trying to use Firebird ODBC (2.0.150) with Open Office 3.3, which claims to only support version 3 of ODBC.

Re: [Firebird-odbc-devel] Connect IBProvider in VB

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

Have done a bit of testing and found that IBProvider was about a third
slower than
the ODBC driver. Will have a go now with fbdll4vb, which is a VB dll
based on the
IBPP Library. If anybody on this list has experience with that then I
would be very
interested.

RBS


On Sun, Mar 6, 2011 at 7:05 AM, Peter Gore
<pe...@go...> wrote:
> Haven't really used ODBC much.  All I can say is that IBProvider "does what
> it says on the tin".
> regards
>
> -----Original Message-----
> From: Bart Smissaert [mailto:bar...@gm...]
> Sent: 05 March 2011 11:30
> To: fir...@li...
> Subject: Re: [Firebird-odbc-devel] Connect IBProvider in VB
>
>
> OK, thanks.
> How did you find IBProvider compared to the ODBC driver?
>
> RBS
>
>
> On Sat, Mar 5, 2011 at 11:18 AM, Peter Gore
> <pe...@go...> wrote:
>> The parameters you selected are the key ones and will certainly suffice
> for
>> your evaluation.
>>
>> -----Original Message-----
>> From: Bart Smissaert [mailto:bar...@gm...]
>> Sent: 05 March 2011 11:13
>> To: fir...@li...
>> Subject: Re: [Firebird-odbc-devel] Connect IBProvider in VB
>>
>>
>> Thanks, I figured this out now.
>> I connected from a string in a text file and that had linebreaks.
>> I thought these linebreaks were dealt with in my code, but they
>> weren't and clearing these
>> linebreaks sorted it out and I can connect fine now.
>> Will have a look at your connection string. Did you find that you
>> needed all those extra parameters or did you find they were
>> beneficial?
>>
>> Do you find that IBProvider is faster than the IB Phoenix ODBC driver?
>>
>> RBS
>>
>> On Sat, Mar 5, 2011 at 10:30 AM, Peter Gore
>> <pe...@go...> wrote:
>>> Why the double backslash in the Data source?
>>>
>>> I use IBProvider and find it great. I use Delphi myself and here is a
>>> typical connection string
>>>
>>> Provider=LCPI.IBProvider.2;Password=MYPASSWORD;Persist Security
>>> Info=True;User ID=MYUSER;Data
>>>
>>
> Source=MyFBData;Location=MyServer:d:\data\fbdata\myfbdata.fdb;ctype=WIN1252;
>>>
>>
> garbage_collect=True;dialect=3;auto_commit=True;auto_commit_level=65536;bicu
>>>
>>
> rsor=False;free_threading=True;array_vt_type=True;inner_trans=True;truncate_
>>>
>>
> char=True;schema_cache=1;support_odbc_query=False;force_prepare_stmt=False;u
>>>
>>
> nicode_mode=True;unicode_stmt=True;std_exec_sp=True;clear_param_info=True;au
>>>
>>
> to_param_describe=True;force_param_describe=True;named_param_prefix=:;ignore
>>>
>>
> _unprepare=True;exec_sp_named_param=False;odbc_call_sp=0;auto_commit_ddl=0;a
>>>
>>
> uto_commit_ddl_level=4096;query_pool_size=8;auto_insert_field_rule=0;auto_up
>>> date_field_rule=0;modify_trans_type=0;modify_trans_level=65536
>>>
>>> Hope this helps
>>>
>>> Regards
>>> peter
>>>
>>> -----Original Message-----
>>> From: Bart Smissaert [mailto:bar...@gm...]
>>> Sent: 05 March 2011 10:23
>>> To: fir...@li...
>>> Subject: [Firebird-odbc-devel] Connect IBProvider in VB
>>>
>>>
>>> I know this is somewhat off-topic, but maybe somebody could tell me
>>> where to get clear instructions how to connect to
>>> Firebird (1.5) with IBProvider in VB, using ADO. I am trying to test
>>> out the free version to see if it might be faster than the
>>> IB Phoenix ODBC driver, but sofar I have been unable to connect.
>>> I copied cc3250mt.dll and _IBProvider_x3_free_i.dll to
>>> C:\WINDOWS\SYSTEM32\ and did a Regsvr32 on the last file.
>>> I have tried various connection strings similar and with all kind of
>>> variations to this one:
>>>
>>> Provider=LCPI.IBProvider.3;
>>> Data Source=localhost:C:\\DB\S6.FDB;
>>> User id=UN;
>>> password=PW;
>>> ctype=win1251;
>>> auto_commit=true
>>>
>>> But sofar no success at all.
>>> I am sure there must be something simple I am doing wrong, but I can't
> see
>>> it.
>>>
>>> RBS
>>>
>>>
>>
> ----------------------------------------------------------------------------
>>> --
>>> What You Don't Know About Data Connectivity CAN Hurt You
>>> This paper provides an overview of data connectivity, details
>>> its effect on application quality, and explores various alternative
>>> solutions. http://p.sf.net/sfu/progress-d2d
>>> _______________________________________________
>>> Firebird-odbc-devel mailing list
>>> Fir...@li...
>>> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>>>
>>>
>>> __________ Information from ESET NOD32 Antivirus, version of virus
>> signature
>>> database 5927 (20110304) __________
>>>
>>> The message was checked by ESET NOD32 Antivirus.
>>>
>>> http://www.eset.com
>>>
>>>
>>>
>>>
>>> __________ Information from ESET NOD32 Antivirus, version of virus
>> signature
>>> database 5927 (20110304) __________
>>>
>>> The message was checked by ESET NOD32 Antivirus.
>>>
>>> http://www.eset.com
>>>
>>>
>>>
>>>
>>>
>>>
>>
> ----------------------------------------------------------------------------
>> --
>>> What You Don't Know About Data Connectivity CAN Hurt You
>>> This paper provides an overview of data connectivity, details
>>> its effect on application quality, and explores various alternative
>>> solutions. http://p.sf.net/sfu/progress-d2d
>>> _______________________________________________
>>> Firebird-odbc-devel mailing list
>>> Fir...@li...
>>> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>>>
>>
>>
> ----------------------------------------------------------------------------
>> --
>> What You Don't Know About Data Connectivity CAN Hurt You
>> This paper provides an overview of data connectivity, details
>> its effect on application quality, and explores various alternative
>> solutions. http://p.sf.net/sfu/progress-d2d
>> _______________________________________________
>> Firebird-odbc-devel mailing list
>> Fir...@li...
>> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
>> database 5927 (20110304) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
>> database 5927 (20110304) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>>
>>
> ----------------------------------------------------------------------------
> --
>> What You Don't Know About Data Connectivity CAN Hurt You
>> This paper provides an overview of data connectivity, details
>> its effect on application quality, and explores various alternative
>> solutions. http://p.sf.net/sfu/progress-d2d
>> _______________________________________________
>> Firebird-odbc-devel mailing list
>> Fir...@li...
>> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>>
>
> ----------------------------------------------------------------------------
> --
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 5927 (20110304) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 5927 (20110304) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 5929 (20110305) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>

Re: [Firebird-odbc-devel] Connect IBProvider in VB

[Peter G. <pe...@go...>]

Haven't really used ODBC much.  All I can say is that IBProvider "does what
it says on the tin".
regards

-----Original Message-----
From: Bart Smissaert [mailto:bar...@gm...] 
Sent: 05 March 2011 11:30
To: fir...@li...
Subject: Re: [Firebird-odbc-devel] Connect IBProvider in VB


OK, thanks.
How did you find IBProvider compared to the ODBC driver?

RBS


On Sat, Mar 5, 2011 at 11:18 AM, Peter Gore
<pe...@go...> wrote:
> The parameters you selected are the key ones and will certainly suffice
for
> your evaluation.
>
> -----Original Message-----
> From: Bart Smissaert [mailto:bar...@gm...]
> Sent: 05 March 2011 11:13
> To: fir...@li...
> Subject: Re: [Firebird-odbc-devel] Connect IBProvider in VB
>
>
> Thanks, I figured this out now.
> I connected from a string in a text file and that had linebreaks.
> I thought these linebreaks were dealt with in my code, but they
> weren't and clearing these
> linebreaks sorted it out and I can connect fine now.
> Will have a look at your connection string. Did you find that you
> needed all those extra parameters or did you find they were
> beneficial?
>
> Do you find that IBProvider is faster than the IB Phoenix ODBC driver?
>
> RBS
>
> On Sat, Mar 5, 2011 at 10:30 AM, Peter Gore
> <pe...@go...> wrote:
>> Why the double backslash in the Data source?
>>
>> I use IBProvider and find it great. I use Delphi myself and here is a
>> typical connection string
>>
>> Provider=LCPI.IBProvider.2;Password=MYPASSWORD;Persist Security
>> Info=True;User ID=MYUSER;Data
>>
>
Source=MyFBData;Location=MyServer:d:\data\fbdata\myfbdata.fdb;ctype=WIN1252;
>>
>
garbage_collect=True;dialect=3;auto_commit=True;auto_commit_level=65536;bicu
>>
>
rsor=False;free_threading=True;array_vt_type=True;inner_trans=True;truncate_
>>
>
char=True;schema_cache=1;support_odbc_query=False;force_prepare_stmt=False;u
>>
>
nicode_mode=True;unicode_stmt=True;std_exec_sp=True;clear_param_info=True;au
>>
>
to_param_describe=True;force_param_describe=True;named_param_prefix=:;ignore
>>
>
_unprepare=True;exec_sp_named_param=False;odbc_call_sp=0;auto_commit_ddl=0;a
>>
>
uto_commit_ddl_level=4096;query_pool_size=8;auto_insert_field_rule=0;auto_up
>> date_field_rule=0;modify_trans_type=0;modify_trans_level=65536
>>
>> Hope this helps
>>
>> Regards
>> peter
>>
>> -----Original Message-----
>> From: Bart Smissaert [mailto:bar...@gm...]
>> Sent: 05 March 2011 10:23
>> To: fir...@li...
>> Subject: [Firebird-odbc-devel] Connect IBProvider in VB
>>
>>
>> I know this is somewhat off-topic, but maybe somebody could tell me
>> where to get clear instructions how to connect to
>> Firebird (1.5) with IBProvider in VB, using ADO. I am trying to test
>> out the free version to see if it might be faster than the
>> IB Phoenix ODBC driver, but sofar I have been unable to connect.
>> I copied cc3250mt.dll and _IBProvider_x3_free_i.dll to
>> C:\WINDOWS\SYSTEM32\ and did a Regsvr32 on the last file.
>> I have tried various connection strings similar and with all kind of
>> variations to this one:
>>
>> Provider=LCPI.IBProvider.3;
>> Data Source=localhost:C:\\DB\S6.FDB;
>> User id=UN;
>> password=PW;
>> ctype=win1251;
>> auto_commit=true
>>
>> But sofar no success at all.
>> I am sure there must be something simple I am doing wrong, but I can't
see
>> it.
>>
>> RBS
>>
>>
>
----------------------------------------------------------------------------
>> --
>> What You Don't Know About Data Connectivity CAN Hurt You
>> This paper provides an overview of data connectivity, details
>> its effect on application quality, and explores various alternative
>> solutions. http://p.sf.net/sfu/progress-d2d
>> _______________________________________________
>> Firebird-odbc-devel mailing list
>> Fir...@li...
>> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
>> database 5927 (20110304) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
>> database 5927 (20110304) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>>
>>
>
----------------------------------------------------------------------------
> --
>> What You Don't Know About Data Connectivity CAN Hurt You
>> This paper provides an overview of data connectivity, details
>> its effect on application quality, and explores various alternative
>> solutions. http://p.sf.net/sfu/progress-d2d
>> _______________________________________________
>> Firebird-odbc-devel mailing list
>> Fir...@li...
>> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>>
>
>
----------------------------------------------------------------------------
> --
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
signature
> database 5927 (20110304) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
signature
> database 5927 (20110304) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
>
----------------------------------------------------------------------------
--
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>

----------------------------------------------------------------------------
--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Firebird-odbc-devel mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel


__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5927 (20110304) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5927 (20110304) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
  

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5929 (20110305) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 

Re: [Firebird-odbc-devel] Connect IBProvider in VB

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

OK, thanks.
How did you find IBProvider compared to the ODBC driver?

RBS


On Sat, Mar 5, 2011 at 11:18 AM, Peter Gore
<pe...@go...> wrote:
> The parameters you selected are the key ones and will certainly suffice for
> your evaluation.
>
> -----Original Message-----
> From: Bart Smissaert [mailto:bar...@gm...]
> Sent: 05 March 2011 11:13
> To: fir...@li...
> Subject: Re: [Firebird-odbc-devel] Connect IBProvider in VB
>
>
> Thanks, I figured this out now.
> I connected from a string in a text file and that had linebreaks.
> I thought these linebreaks were dealt with in my code, but they
> weren't and clearing these
> linebreaks sorted it out and I can connect fine now.
> Will have a look at your connection string. Did you find that you
> needed all those extra parameters or did you find they were
> beneficial?
>
> Do you find that IBProvider is faster than the IB Phoenix ODBC driver?
>
> RBS
>
> On Sat, Mar 5, 2011 at 10:30 AM, Peter Gore
> <pe...@go...> wrote:
>> Why the double backslash in the Data source?
>>
>> I use IBProvider and find it great. I use Delphi myself and here is a
>> typical connection string
>>
>> Provider=LCPI.IBProvider.2;Password=MYPASSWORD;Persist Security
>> Info=True;User ID=MYUSER;Data
>>
> Source=MyFBData;Location=MyServer:d:\data\fbdata\myfbdata.fdb;ctype=WIN1252;
>>
> garbage_collect=True;dialect=3;auto_commit=True;auto_commit_level=65536;bicu
>>
> rsor=False;free_threading=True;array_vt_type=True;inner_trans=True;truncate_
>>
> char=True;schema_cache=1;support_odbc_query=False;force_prepare_stmt=False;u
>>
> nicode_mode=True;unicode_stmt=True;std_exec_sp=True;clear_param_info=True;au
>>
> to_param_describe=True;force_param_describe=True;named_param_prefix=:;ignore
>>
> _unprepare=True;exec_sp_named_param=False;odbc_call_sp=0;auto_commit_ddl=0;a
>>
> uto_commit_ddl_level=4096;query_pool_size=8;auto_insert_field_rule=0;auto_up
>> date_field_rule=0;modify_trans_type=0;modify_trans_level=65536
>>
>> Hope this helps
>>
>> Regards
>> peter
>>
>> -----Original Message-----
>> From: Bart Smissaert [mailto:bar...@gm...]
>> Sent: 05 March 2011 10:23
>> To: fir...@li...
>> Subject: [Firebird-odbc-devel] Connect IBProvider in VB
>>
>>
>> I know this is somewhat off-topic, but maybe somebody could tell me
>> where to get clear instructions how to connect to
>> Firebird (1.5) with IBProvider in VB, using ADO. I am trying to test
>> out the free version to see if it might be faster than the
>> IB Phoenix ODBC driver, but sofar I have been unable to connect.
>> I copied cc3250mt.dll and _IBProvider_x3_free_i.dll to
>> C:\WINDOWS\SYSTEM32\ and did a Regsvr32 on the last file.
>> I have tried various connection strings similar and with all kind of
>> variations to this one:
>>
>> Provider=LCPI.IBProvider.3;
>> Data Source=localhost:C:\\DB\S6.FDB;
>> User id=UN;
>> password=PW;
>> ctype=win1251;
>> auto_commit=true
>>
>> But sofar no success at all.
>> I am sure there must be something simple I am doing wrong, but I can't see
>> it.
>>
>> RBS
>>
>>
> ----------------------------------------------------------------------------
>> --
>> What You Don't Know About Data Connectivity CAN Hurt You
>> This paper provides an overview of data connectivity, details
>> its effect on application quality, and explores various alternative
>> solutions. http://p.sf.net/sfu/progress-d2d
>> _______________________________________________
>> Firebird-odbc-devel mailing list
>> Fir...@li...
>> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
>> database 5927 (20110304) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
>> database 5927 (20110304) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>>
>>
> ----------------------------------------------------------------------------
> --
>> What You Don't Know About Data Connectivity CAN Hurt You
>> This paper provides an overview of data connectivity, details
>> its effect on application quality, and explores various alternative
>> solutions. http://p.sf.net/sfu/progress-d2d
>> _______________________________________________
>> Firebird-odbc-devel mailing list
>> Fir...@li...
>> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>>
>
> ----------------------------------------------------------------------------
> --
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 5927 (20110304) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 5927 (20110304) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>