|
|
|
date: Wed, 03 May 2006 15:58:48 +0200,
group: microsoft.public.access.odbcclientsvr
back
Re: MySQL -> ODBC -> XP64
Asgeir,
See here for the connection string syntax:
http://www.connectionstrings.com/
In version 3.51, UID should be USER and PWD should be PASSWORD
Also, I have had many issues with linked tables and the MySQL ODBC
driver. I'm not sure if it is applicable for you, but I include it just
in case -
Version 3.51.12 does not always work; but version 3.51.09 works for me.
The password is cached in the connection string, no matter what you do.
After you link the table, look at the connection string. Even if you
did not check "save password", it will be there in clear text. This is
a major bug and as a result you must protect the Access file where the
linked table is.
Good luck,
Mattias
From: Asgeir Nesoen, on 5/3/2006 9:58 AM:
> Has anyone managed to get the MySQL ODBC drivers (3.51.12) to work on a
> XP64 box?
>
> I create a sample DSN from the syswow64 version of the odbcad32.exe, and
> when testing the connection (from the MySQL DSN definition screen), the
> thing says "Success; connection was made", so everything seems to be
> working fine.
>
> I then try to preconnect to the server by doing:
> Dim db As Database
> strConnectString = "ODBC;DRIVER={MySQL ODBC 3.51 Driver};SERVER=" &
> strServer & ";DATABASE=" & strDBName & ";UID=" & strUserID & ";PWD=" &
> strPassWord
> Set db = OpenDatabase("", dbDriverNoPrompt, False, strConnectString)
> db.Close,
> and Access crashes...
>
> Anyone out there with any idea? Do I need to use a special syntax when
> declaring the driver to use in the connection string? In order to use
> the 32-bit drivers, I mean?
>
> ---Asgeir---
date: Wed, 03 May 2006 11:24:30 -0400
author: Mattias Jonsson
Re: MySQL -> ODBC -> XP64
I may not have been entirely clear about my problem.
The thing is, everything works like a charm on a XP pro box, with the
3.51.12 ODBC drivers. So the connection string works.
And I was wondering if I need to adjust my connection string in any way
to get it to work on a *XP64* box with the same drivers. I have seen
reported problems with the MySQL ODBC drivers on XP64, but I wanted to
check here before reinstalling my workstation with XP pro...
I have also been extremly annoyed with the pop-up over the tables, with
the plain text password displayed. This is a serious bug, but I guess MS
are the ones that have to fix it. Why someone would ever come up with
the idea of displaying the entire connection string by way of a pop-up
is totally beyond me, hehe.
Luckily, my users are so stupid they wouldn't know what to do with a
cleartext password anyway, hehehe.
---A---
On 03.05.2006 17:24, Mattias Jonsson wrote:
> Asgeir,
> See here for the connection string syntax:
> http://www.connectionstrings.com/
>
> In version 3.51, UID should be USER and PWD should be PASSWORD
>
> Also, I have had many issues with linked tables and the MySQL ODBC
> driver. I'm not sure if it is applicable for you, but I include it just
> in case -
>
> Version 3.51.12 does not always work; but version 3.51.09 works for me.
>
> The password is cached in the connection string, no matter what you do.
> After you link the table, look at the connection string. Even if you
> did not check "save password", it will be there in clear text. This is
> a major bug and as a result you must protect the Access file where the
> linked table is.
>
> Good luck,
> Mattias
>
> From: Asgeir Nesoen, on 5/3/2006 9:58 AM:
>
>> Has anyone managed to get the MySQL ODBC drivers (3.51.12) to work on
>> a XP64 box?
>>
>> I create a sample DSN from the syswow64 version of the odbcad32.exe,
>> and when testing the connection (from the MySQL DSN definition
>> screen), the thing says "Success; connection was made", so everything
>> seems to be working fine.
>>
>> I then try to preconnect to the server by doing:
>> Dim db As Database
>> strConnectString = "ODBC;DRIVER={MySQL ODBC 3.51 Driver};SERVER=" &
>> strServer & ";DATABASE=" & strDBName & ";UID=" & strUserID & ";PWD=" &
>> strPassWord
>> Set db = OpenDatabase("", dbDriverNoPrompt, False, strConnectString)
>> db.Close,
>> and Access crashes...
>>
>> Anyone out there with any idea? Do I need to use a special syntax when
>> declaring the driver to use in the connection string? In order to use
>> the 32-bit drivers, I mean?
>>
>> ---Asgeir---
date: Thu, 04 May 2006 09:35:17 +0200
author: Asgeir Nesoen
Re: MySQL -> ODBC -> XP64
I found the solution to this problem an hour ago...
This problem exists for XP64 and W2003 alike, and the cause is a bug in
the MSJet40 version of the standard XP64 installation. I am sure the
same bug exists in a wide variety of MDAC packages, servicepacks and
patches. Version 4.0.9025.0 simply doesn't work with MySQL, and neither
MS nor MySQL have done anything about it.
I downgraded my MSJet40 version to version 4.0.8618.0 by copying the
appropriate MSJet40.dll file into my access installation directoy, and
everything worked like a charm. Windows applications look for any
library file locally before it uses the system library files.
This routine has a downside; Version .8618 was upgraded by MS to .9025
due to a security hole. But I would think that only using the
MSJet40.dll in the access directory would present a minimal security
risk since it is not installed as the system MSJet40.dll. It'd be nice
if someone who actually knows anything about this security hole would
come back with info on this, though...
---Asgeir---
On 04.05.2006 09:35, Asgeir Nesoen wrote:
> I may not have been entirely clear about my problem.
>
> The thing is, everything works like a charm on a XP pro box, with the
> 3.51.12 ODBC drivers. So the connection string works.
>
> And I was wondering if I need to adjust my connection string in any way
> to get it to work on a *XP64* box with the same drivers. I have seen
> reported problems with the MySQL ODBC drivers on XP64, but I wanted to
> check here before reinstalling my workstation with XP pro...
>
> I have also been extremly annoyed with the pop-up over the tables, with
> the plain text password displayed. This is a serious bug, but I guess MS
> are the ones that have to fix it. Why someone would ever come up with
> the idea of displaying the entire connection string by way of a pop-up
> is totally beyond me, hehe.
>
> Luckily, my users are so stupid they wouldn't know what to do with a
> cleartext password anyway, hehehe.
>
> ---A---
>
> On 03.05.2006 17:24, Mattias Jonsson wrote:
>
>> Asgeir,
>> See here for the connection string syntax:
>> http://www.connectionstrings.com/
>>
>> In version 3.51, UID should be USER and PWD should be PASSWORD
>>
>> Also, I have had many issues with linked tables and the MySQL ODBC
>> driver. I'm not sure if it is applicable for you, but I include it
>> just in case -
>>
>> Version 3.51.12 does not always work; but version 3.51.09 works for me.
>>
>> The password is cached in the connection string, no matter what you
>> do. After you link the table, look at the connection string. Even if
>> you did not check "save password", it will be there in clear text.
>> This is a major bug and as a result you must protect the Access file
>> where the linked table is.
>>
>> Good luck,
>> Mattias
>>
>> From: Asgeir Nesoen, on 5/3/2006 9:58 AM:
>>
>>> Has anyone managed to get the MySQL ODBC drivers (3.51.12) to work on
>>> a XP64 box?
>>>
>>> I create a sample DSN from the syswow64 version of the odbcad32.exe,
>>> and when testing the connection (from the MySQL DSN definition
>>> screen), the thing says "Success; connection was made", so everything
>>> seems to be working fine.
>>>
>>> I then try to preconnect to the server by doing:
>>> Dim db As Database
>>> strConnectString = "ODBC;DRIVER={MySQL ODBC 3.51 Driver};SERVER=" &
>>> strServer & ";DATABASE=" & strDBName & ";UID=" & strUserID & ";PWD="
>>> & strPassWord
>>> Set db = OpenDatabase("", dbDriverNoPrompt, False, strConnectString)
>>> db.Close,
>>> and Access crashes...
>>>
>>> Anyone out there with any idea? Do I need to use a special syntax
>>> when declaring the driver to use in the connection string? In order
>>> to use the 32-bit drivers, I mean?
>>>
>>> ---Asgeir---
date: Thu, 04 May 2006 15:44:03 +0200
author: Asgeir Nesoen
|
|
