problem with Chinese regional option and MySQL

[ChrisM]

Hi there. We have a problem where if the Advanced regional language setting 'Language for non-unicode programs' is set to Chinese PRC (the other settings are both set to UK), we get an error when trying to import a package into the MySQL repository.
The error is 'multiple-step operation generated errors. check status of each value'.
If a local EAP file is used instead it works fine.

We are using EA 7.5.845, Windows XP SP3, MySQL server 5.0.51b, ODBC connector 3.51.25.

Any ideas? Someone suggested changing the SQL tables to use utf8 encoding instead of latin1, but so far that has made no difference.

[Eve]

ODBC 3.51 drivers don't support unicode.  We have a couple of databases here on MySQL 5.1 and connecting with version 5.1.5 of the odbc driver.  I'd recommend giving that a try.  (At least an updated odbc driver)

[ChrisM]

Thanks for the reply. I tried the updated driver but got the same response.
Using an ODBC sniffer showed that the import failed when trying to update the connectors. It looks like the SourceStyle and DestStyle are being incorrectly read (or converted) from the XML file.
Examination of the xml file shows no Unicode characters (and definitely no Chinese characters).
Are there any settings in EA I can check as it looks like the conversion is down to EA and not the driver?

[Eve]

Don't know then.  You'll have to send a bug report to Sparx Systems.  If you can attach the XMI file that will help a lot.

[ChrisM]

Thanks. I have raised a bug report.

[Jonathan@Logica]

A year later and one of my colleagues has had the same problem.
It seems that there's an option in the current MySQL ODBC connector that allows you to not use setLocale.

This seems to have done the trick