Cannot access tables in mysql db using Crystal Reports v9

I also just saw where this was a known issue w/ Crystal and mysql at one time ( http://support.businessobjects.com/library/kbase/articles/c2013269.asp ).  If you haven't already applied all of the hotfixes and updates then you should do that first and that alone may resolve the problem.

Frodoman,

First of all - thanks for such a thoughtful, quick, and helpful reply.

I had already done all of your first suggestions, but the second suggestion was spot-on. The article you linked me to was EXACTLY my problem!

However, there is some good news and bad news.

Having carefully installed the patch (ie I installed only the bits that the accompanying pdf file told me I needed - namely an updated ODBC driver) I can now see the tables as expected. That's the good news.

The bad news is that I cannot access them, because attempting to include any of the tables from the database throws the following error:

Query Engine Error:'HYCOO:[MySql][ODBC 3.51 Driver][mysqld-3.23.57-nt] Can't use wildcards in table name'

This is odd, because I haven't used any wildcards in the table names. They're called simple things like "questions" and "answers". However, my database name has some underscores in it, and I wonder if it's these underscores that are causing the problems?

I hope not, because changing the database name has a number of other consequences across an operational website...

Do you have any other ideas about what might be throwing this error?  Or do you recommend that I install ALL of the stuff in the hotfix bundle in the hope that something other than the driver was causing the issue?  My concern about doing the latter is that there's some pretty esoteric stuff in there, which seems to require manual editing of Registry entries - and that's something I definitely want to avoid if possible.

Thanks again for your help so far - it's clear that we're on the right lines, even if one or two wheels seem to have fallen off along the way!

Regards

Grummy

A bit more info...

I've just tried creating a new dummy database, without underscores or spaces in the db name - and tried to access a table within it.

Exactly the same error occurs, so I guess we can rule out the underscores as a contributory factor...

G

That worked a treat!

Many thanks for your expert help - it would have taken me ages to find the right place to look for this patch if you hadn't pointed me in its direction.

Your help has been well-worth my membership money!

Much appreciated.

Best regards

Graham