MySQL Bugs: #34908: Not possible to create a table link towards a 32 bit application (e.g. MsAccess)

Bug #34908	Not possible to create a table link towards a 32 bit application (e.g. MsAccess)
Submitted:	27 Feb 2008 21:33	Modified:	9 Apr 2008 19:27
Reporter:	Louis Breda van	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	5.1.2	OS:	Windows (VISTA64)
Assigned to:	Georg Richter	CPU Architecture:	Any
Tags:	32bit, tablelink, vista64

Description:
Hello,

I need a table link from MsAcces (32-bit) towards MySqlServer 64 bit (5.1.2.3). Using the latest 5.1.x 64 bit ODBC-driver.

I do not manage to create that needed link.

Note that:
- I can setup the table link when using ODBC 3.5 32 bit
- I can access the 64 bit MySql Sever engine from MsAccess VBA

However, I need both access by VBA as well as access by a table link. Reason for that is that the only way to join a MySQL based recordset with a MsAccees recordset is by using a table link.

This is almost if not completely a showstopper for me since:
a) in some cases I need 5.1 functionallity, so I can not / only partly go back to 3.5
(b) I need to sacrify performance by going back to 32 bit odbc)

Hope to have this fixed soon.

Sincerely,

Louis

How to repeat:
Install ODBC 5.1 64 bit

Try to create a table link from within MsAccess
- Open MsAccess table plane (e.g. access 2007)
- access gui: import ODBC DB
- option create a linked table
- select data source choose computer data source option new
- choose mySQL ODBC 5.1 driver + next
- mysql data source configurator window pops up
- choose name e.g. ape discription e.g. ape server localhost (in my case), user e.g. root rootpw
==> here you already see the problem, you can not select a db
==> you can not connect to the db

Try to create the link as system or user DSN from
configscreen 32bit odbc configurator
==> fails in the same way.

Try to create a DSN from the 64 bit configscreen ODBC configurator
==> does work, but that is not the one needed

Doing the same with odbc 3.51 driver works perfect and
It is *not* working with 32 bit version of 5.1 as well

Louis, I do get the problem but I need to get license for new office first.

Just a remark:
> (b) I need to sacrify performance by going back to 32 bit odbc) 

You are not sacrifying anything as entire Office is 32bit app and will refuse any 64 bit driver DSN. It can only use DSN made with 32bit driver, either 3.51 or 5.1. And as I said in previous report, *both* 64bit and 32bit 5.1 drivers are installed with same setup on Winx64. Maybe you are confused by the fact that both 32 and 64bit c/ODBC 5.1 drivers have same name (and even their DSN's can have same names as they are kept in separate parts of registry) but don't worry, that confuses me too, sometimes :)

MS-Access is a 32-bit applicaton, so you will need a 32-bit driver. Latest MSI for Windows 64-bit provides both 32-bit and 64-bit driver.

impossible to create a table link using odbc V5

Attachment: odbcversion5doesnotworks.gif (image/gif, text), 13.87 KiB.

as it should, table link creation with ODBC V3

Attachment: odbcversion3works.gif (image/gif, text), 17.73 KiB.

Sorry,

Table link creation using ODBC V5 (latest version), simply does not work, where it should work !!

Also see the screen captures send from ODBC V3 (works) and V5 (does not work) !

Again, hope to have this fixed soon.

Sincerely,

Louis

From a post by Pascal Deliot:

It's important to understand which kind of DSN you have. On an x64 system,
you can create an ODBC connection(DSN) on the 32-bit side of the system or
on the 64-bit side of the system.

32-bit applications will only see ODBC connections created in the 32-bit
side, and 64-bits applications will only see ODBC connections from the
64-bit side. Each kind of application has is own registry.

To setup DSN for 32-bit application you must use:
%WINDIR%\SysWOW64\odbcad32.exe
and for 64-bit application you must use:
%WINDIR%\System32\odbcad32.exe

Thank you Christopher. We encourage and welcome community feedbacks such as these.

Now, Christopher's explanation is repeated all over bugsdb and, afaik, in manual. Be careful as system folders naming is all messed up by Microsoft due to backward compatibility I believe.