the issue may be in the ODBC, but not in Qlik.
I remember I specified sometime ago the codepage for odbc connection. It make me think that it can have only one codepage in a moment.
That's why I would advise to try OLEDB driver and connection. I haven't heard about such kind of limitations there.
This is just my guess, but it worth to try
I will take a look - but I believe this has something to do with your character set or codepage similar to what Sergey mentioned.
Can you check out this thread utf 8 - MySQL UTF8 Data Not Being Displayed Properly - Stack Overflow and let me know how you do?
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.