RE: How to treat the SET type field?
"Bonnett, John" <[email protected]> Tue, 25 Feb 2014 09:46:15 +0800
| Newsgroups | gmane.comp.db.mysql.odbc |
|---|---|
| Message-ID | <0F231A06CA35674FAB1E114AEE8D5E647C5B472C3F@sgsi6sexh01> |
Hi Hirobon, 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 cas= e as if you might be able to get access to the MySQL SET/ENUM columns in Ac= cess if the ODBC drive allowed it. I have no experience modifying the ODBC driver. It is probably C++, which i= s a language I have not worked with much. If you wanted to have a go, the f= irst 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 usef= ul you would want any changes to not cause a problem for anyone not using A= ccess as the client. That's how open source is supposed to work. ________ Carl Zeiss Vision Australia (Asia Pacific) Global Business Solutions/Customer Enablement Software Engineer J o h n B o n n e t t Phone: +61 (0) 8 8392 8307 Fax: +61 (0) 8 8392 8160 Mailto: [email protected] www.zeiss.com/vision This email, including any attachments, is intended for the sole use of the = intended recipient(s) and may contain information that is confidential, pri= vileged and/or the sender=1B$B!G=1B(Bs work. Any review or distribution by any other person is prohibited. If you are no= t an intended recipient, please immediately contact the sender and delete a= ll copies. -----Original Message----- From: =1B$B=3DE!!Gn8w=1B(B [mailto:[email protected]] Sent: Tuesday, 25 February 2014 11:57 AM To: Bonnett, John; [email protected] Subject: Re: How to treat the SET type field? Hi John! Thank you for your help. I also googled this issue. And I found this articl= e. http://office.microsoft.com/en-us/access-help/using-multivalued-fields-in-q= ueries-HA010149297.aspx?CTT=3D1 It says that access2007 can treat multivalued field. I think this problem causes that MySQL/ODBC connector can not convert SET t= ype field to Access2013 multivalued field. If you know how to change the source code of ODBC driver, please tell me th= at. Thank you for any help. hirobon. --------------- This message is intended for a particular addressee only and may contain bu= siness or company secrets. If you have received this email in error, please contact the sender and del= ete the message immediately. Any use of this email, including saving, publi= shing, copying, replication or forwarding of the message or the contents is= not permitted. -- MySQL ODBC Mailing List For list archives: http://lists.mysql.com/myodbc To unsubscribe: http://lists.mysql.com/myodbc