Qlik Community

QlikView App Dev

Discussion Board for collaboration related to QlikView App Development.

Announcements
Customer & Partners, DEC. 9, 11 AM ET: Qlik Product & Strategy Roadmap Session: Data Analytics REGISTER NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

OBDC Issue, when trying to connect to mysql

I'm trying to connect to my MYSQL database through ODBC, but when I try to connect - I get this message

Skærmbillede 2012-07-03 kl. 18.17.39.png

When I close the message - Im still directed to the select window, but Im not able to see any other info that the tables in the database:

Skærmbillede 2012-07-03 kl. 18.18.53.png

Can somebody help me - I have tried on XP and Windows 7 and it's the same issue?

1 Solution

Accepted Solutions
jjfabian
Partner
Partner

Hi again,

all ODBC driver versions can be found on this page.

http://dev.mysql.com/downloads/connector/odbc/5.0.html

View solution in original post

14 Replies
Not applicable
Author

No one who is able to help?

Not applicable
Author

check Force 32 Bit option and try

Not applicable
Author

I have done that, but it's the same issue

jjfabian
Partner
Partner

Hi there,

so I finally mynaged to recreate your problem. On my machine it seems to be occuring when you attempt to access an empty table within the MySQL (in this database I have 6 tables, one of them which is currently empty. I only get the problem when I try to select that one).

So, the question is, do you have any empty tables in your MySQL?

If that is the case, then maybe this is a bug of some sort

Best regards, Jakob

Edit: If this is indeed caused by a specific table, have you tried loading the data by manually writing LOAD *; SQL SELECT * from yourtable

jjfabian
Partner
Partner

I've made another observation here: now, the table is not empty anymore, but contains non-standard characters. Seems to cause the crash. I'll keep you posted as I discover more.

Not applicable
Author

Even I am facing the same issue ..

Regards,

Mandar

jjfabian
Partner
Partner

Hi everyone,

found a solution that works for me.

Previously, I was using the 5.1.11 MySQL ODBC drivers.

Switched to the 5.1.9 Version of the driver, now it works just fine for me.

Regards, Jakob

Not applicable
Author

I can´t find that driver - do you have a link?

jjfabian
Partner
Partner

I can't find the link either. I pulled it from my company's software drive.

I've attached the file, so that you can test if it solves your problem.

I'll supply a direct download link if I can find one.

Jakob