I was not aware of those multi-valued fields in Access.
I agree, I think the issue will be in the ODBC connector. ODBC is supposed to be a method
for connecting to all sorts of databases and accordingly it mostly only supports things
that are widely available. It looks in this case as if you might be able to get access to
the MySQL SET/ENUM columns in Access if the ODBC drive allowed it.
I have no experience modifying the ODBC driver. It is probably C++, which is a language I
have not worked with much. If you wanted to have a go, the first step would be to see if
you could at least build a working version of the driver yourself. If you can do that, and
get familiar with how it works, you could try modifying it to do what you want. To make it
generally useful you would want any changes to not cause a problem for anyone not using
Access as the client. That's how open source is supposed to work.
Carl Zeiss Vision Australia (Asia Pacific)
Global Business Solutions/Customer Enablement
J o h n B o n n e t t
Phone: +61 (0) 8 8392 8307
Fax: +61 (0) 8 8392 8160
This email, including any attachments, is intended for the sole use of the intended
recipient(s) and may contain information that is confidential, privileged and/or the
Any review or distribution by any other person is prohibited. If you are not an intended
recipient, please immediately contact the sender and delete all copies.
From: 重 博光 [mailto:hirobon@stripped]
Sent: Tuesday, 25 February 2014 11:57 AM
To: Bonnett, John; myodbc@stripped
Subject: Re: How to treat the SET type field?
Thank you for your help. I also googled this issue. And I found this article.
It says that access2007 can treat multivalued field.
I think this problem causes that MySQL/ODBC connector can not convert SET type field to
Access2013 multivalued field.
If you know how to change the source code of ODBC driver, please tell me that.
Thank you for any help.
This message is intended for a particular addressee only and may contain business or
If you have received this email in error, please contact the sender and delete the message
immediately. Any use of this email, including saving, publishing, copying, replication or
forwarding of the message or the contents is not permitted.