Catastrphic failure in Delphi with new ODBC Connector

------=_NextPart_000_0007_01C5352A.0408A0A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I've had a Delphi app working well using an TADOConnection and the ODBC =
Connector version 3.51.8.
I removed that connector and installed version 3.51.10. It connects =
successfully from the DNS but when I try to connect from Delphi I get =
"Catastrophic failure". I outstalled this version and tried 3.51.11 =
with the same result. What could be the problems here? I can't find =
anything about it at MySQL.com

------=_NextPart_000_0007_01C5352A.0408A0A0--
Billy Yard [ Mi, 30 März 2005 19:11 ] [ ID #721024 ]

Re: Catastrphic failure in Delphi with new ODBC Connector

Billy Yard wrote:

>I've had a Delphi app working well using an TADOConnection and the ODBC Connector version 3.51.8.
>I removed that connector and installed version 3.51.10. It connects successfully from the DNS but when I try to connect from Delphi I get "Catastrophic failure". I outstalled this version and tried 3.51.11 with the same result. What could be the problems here? I can't find anything about it at MySQL.com
>
>
>
Please try 3.51.11.x

--
Peter Harvey, Software Developer
MySQL AB, www.mysql.com

Are you MySQL certified? www.mysql.com/certification



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org
pharvey [ Mi, 30 März 2005 19:40 ] [ ID #721025 ]

Re: Catastrphic failure in Delphi with new ODBC Connector - FIXED

I've resolved the problem and the fix is easy if not somewhat peculiar. It
seems TADOConnection provides TMI to the connector. When you use the build
wizard it creates a string with info for
Provider, Persistent Security Info, User ID, Data Source and Initial
Catalog. On attempting to connect you get a catastrophic error. If you
remove the Initail Catalog parameter and try to connect then the connection
is successful and the connection string is replaced with one containing:
Provider, Persistent Security Info, User ID, Data Source and Extended
Properties consisting of:
DATABASE, DESCRIPTION, DSN, OPTION, PORT, SERVER & UID.
Hope this is helpful for the next release.


> Billy Yard wrote:
>
>>I've had a Delphi app working well using an TADOConnection and the ODBC
>>Connector version 3.51.8.
>>I removed that connector and installed version 3.51.10. It connects
>>successfully from the DNS but when I try to connect from Delphi I get
>>"Catastrophic failure". I outstalled this version and tried 3.51.11 with
>>the same result. What could be the problems here? I can't find anything
>>about it at MySQL.com
>>
>>
> Please try 3.51.11.x
>
> --
> Peter Harvey, Software Developer
> MySQL AB, www.mysql.com
>
> Are you MySQL certified? www.mysql.com/certification
>
>
>
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe:
> http://lists.mysql.com/myodbc?unsub=chris.tatedavies [at] ceta.co .uk
>
>
>
>
>
> Central Electronic Trading Agency Limited , authorised and regulated by
> the Financial Services Authority.
>
>



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org
Billy Yard [ Mi, 30 März 2005 22:48 ] [ ID #721027 ]
Datenbanken » gmane.comp.db.mysql.odbc » Catastrphic failure in Delphi with new ODBC Connector

Vorheriges Thema: ODBC Connector override via VB
Nächstes Thema: SQLConnect problem