: problem using mysql odbc with windows and access

-------------------------------1133258502
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
Hi,
=20
I am testing MySQL, I am using actually Microsof Access 2000 and Windows 20=
00
I create a database from Access to MySQL with the migration toolkit, worked=
=20
fine.=20
I try to attach a MySQL table with Access using ODBC.=20
I installed mysql-connector-odbc-3.51.12=20

In the connection dialog, Access is asking for "Mysql ODBC 3.51 Driver"=20
in the list given by Windows there is "Mysql Connector/ODBC 3.51"=20

when I try the connection I have the error message:=20

[MySQL][ODBC 3.51 Driver] Could not find driver {MySQL ODBC 3.51 Driver} in=
=20
System information. (#0)=20

If I try to change the name in the .dsn file using the second name I have a=
n=20
other error message: =20

[Microsoft][Gestionnaire de pilotes ODBC] Source de donn=E9es introuvable e=
t=20
nom de pilote non sp=E9cifi=E9 (#0)=20

What should I do? As you noticed I am french and the second message comes=20
from my microsoft product which is installed in french!=20
Many Thanks in advance
Dominique Clauzel
Grenoble, France


-------------------------------1133258502--

RE: : problem using mysql odbc with windows and access

Dominique Clauzel wrote:
> I try to attach a MySQL table with Access using ODBC.
> I installed mysql-connector-odbc-3.51.12
>=20
> In the connection dialog, Access is asking for "Mysql ODBC 3.51 =
Driver"
> in the list given by Windows there is "Mysql Connector/ODBC 3.51"

Which list? Add/Remove programs?
That's just a descriptive name, not the ODBC driver name.

If you want the installed driver's name, look in:
Control Panel -> Administrative Tools -> Data Sources (ODBC), or
Start -> Run: "odbccp32.cpl"

> [MySQL][ODBC 3.51 Driver] Could not find driver {MySQL ODBC 3.51 =
Driver} in
> System information. (#0)

Not sure why the ODBC driver would be "looking for itself".

Seems there's a superfluous space character between "ODBC" and "3.51" =
though,
perhaps that's your problem?

> If I try to change the name in the .dsn file using the second name I =
have an
> other error message:
>=20
> [Microsoft][Gestionnaire de pilotes ODBC] Source de donn=E9es =
introuvable et
> nom de pilote non sp=E9cifi=E9 (#0)

Probably because "MySQL ODBC 3.51 Driver" is the correct ODBC driver =
name and
you're using "Mysql Connector/ODBC 3.51"..


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

Re: : problem using mysql odbc with windows and access

-------------------------------1133267167
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
Thank you for your answer,
=20
Dans un e-mail dat=E9 du 29/11/2005 12:10:00 Paris, Madrid, ddi@dubex.dk a =20
=E9crit :

Dominique Clauzel wrote:
> I try to attach a MySQL table with Access using ODBC.
> I installed mysql-connector-odbc-3.51.12
>=20
> In the connection dialog, Access is asking for "Mysql ODBC 3.51 Driver"
> in the list given by Windows there is "Mysql Connector/ODBC 3.51"

Which list? Add/Remove programs?
That's just a descriptive name, not the ODBC driver name.

If you want the installed driver's name, look in:
Control Panel -> Administrative Tools -> Data Sources (ODBC), or
Start -> Run: "odbccp32.cpl"

> [MySQL][ODBC 3.51 Driver] Could not find driver {MySQL ODBC 3.51 Driver}=
=20
in
> System information. (#0)

Not sure why the ODBC driver would be "looking for itself".

Seems there's a superfluous space character between "ODBC" and "3.51" thoug=
h,
perhaps that's your problem?
What I try to do is the following:
From access I try to link a table through the menu, I say "ODBC" and I have=20=
=20
to give a file .dsn name.
This file contains the followoing:
[ODBC]
DRIVER=3DMySQL ODBC 3.51 Driver
If I look into the register of Windows, in the section:
HKEY_LOCAL_MACHINE\SOFTWARE_ODBC\ODBCINST.INI
there is an entry "MySQL ODBC 3.51 Driver" and this entry contains 4 items:
first one: nothing
second: Driver C:\WINNT\System32\myodbc3.dll (it exists, I checked)
third: Setup C:\WINNT\System32\Myodbc35.dll (it exists, Ichecked)
forth: Usagecount 0x00000001
=20
There is no extra space anywhere. Do you have any idea?=20
Many thanks in advanceDominique=20



> If I try to change the name in the .dsn file using the second name I hav=
e=20
an
> other error message:
>=20
> [Microsoft][Gestionnaire de pilotes ODBC] Source de donn=E9es introuvable=
=20
et
> nom de pilote non sp=E9cifi=E9 (#0)

Probably because "MySQL ODBC 3.51 Driver" is the correct ODBC driver name a=
nd
you're using "Mysql Connector/ODBC 3.51"..
I agree, the correct name is the first one. You are correct.
Dominique Clauzel
Grenoble, France

-------------------------------1133267167--

Re: : problem using mysql odbc with windows and access

Idclauzel@aol.com wrote:

>
>Hi,
>
>I am testing MySQL, I am using actually Microsof Access 2000 and Windows 2000
>I create a database from Access to MySQL with the migration toolkit, worked
>fine.
>I try to attach a MySQL table with Access using ODBC.
>I installed mysql-connector-odbc-3.51.12
>
>In the connection dialog, Access is asking for "Mysql ODBC 3.51 Driver"
>in the list given by Windows there is "Mysql Connector/ODBC 3.51"
>
>when I try the connection I have the error message:
>
>[MySQL][ODBC 3.51 Driver] Could not find driver {MySQL ODBC 3.51 Driver} in
>System information. (#0)
>
>If I try to change the name in the .dsn file using the second name I have an
>other error message:
>
>[Microsoft][Gestionnaire de pilotes ODBC] Source de données introuvable et
>nom de pilote non spécifié (#0)
>
>What should I do? As you noticed I am french and the second message comes
>from my microsoft product which is installed in french!
>Many Thanks in advance
>Dominique Clauzel
>Grenoble, France
>
>
>
>
1. Try to use a regular DSN for this (not a File DSN).
2. You should be using a patched version from;
ftp.mysql.com/pub/mysql/hidden/connectors/odbc as a fix for
SQLDriverConnect has not been published yet.

The reason why the driver looks for itself under certian circumstances
is because it wants to know what its setup library (thats the gui bits)
is. It does not assume to be using the specific one we have made for it.

--
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@m.gmane.org