Bug #30299 Using mysql odbc connector in crystal reports XI
Submitted: 8 Aug 2007 9:58 Modified: 17 Sep 2007 5:53
Reporter: Ziyaad Sayed Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:3.51.17 OS:Windows
Assigned to: CPU Architecture:Any

[8 Aug 2007 9:58] Ziyaad Sayed
Description:
Hi. My name is Ziyaad

Previously using ODBC 3.51.15, crystal reporting XI would crash when trying to connect. This issue was reported and i was advised that the problem would be rectified with the release of ODBC 3.51.17. Crystal Reporting now connects to the mysql database without any fatal crashes using 3.51.17, however the problem is that some fields in a table are missing when browsing in crystal reporting XI. My OS is Win XP Pro

Please advise. 

Thanks.

How to repeat:
Install Crystal Reporting Developer XI and try to connect to a mysql database using ODBC 3.51.17

OS Platform is XP Pro Service Pack 2
[28 Aug 2007 11:31] Tonci Grgin
Hi Ziyaad and thanks for your report. Sorry for the delay in processing, I missed it somehow...

Can you please attach:
 - my.ini / my.cnf file
 - table definition and some data suitable for import
 - CR report used for displaying of that data showing the problem
[3 Sep 2007 12:00] Ziyaad Sayed
Hi Tonci.

I see that version 3.51.19 has been released. I will try uins this ODBC connector and if there are any problems i will create a new report for ODBC 3.51.19. 

Thanks

Ziyaad
[3 Sep 2007 13:35] Tonci Grgin
Ziyaad, please do as we have increased our efforts on MyODBC greatly. Waiting on your result.
[17 Sep 2007 0:52] Craig Everard
Hi,

I had exactly the same issue with Crystal Reports XI. I was using MySQL ODBC 3.51
.17, then I upgraded to 18 and 19 respectively and got 1064 error instead. Today I upgraded to 3.51.20 and it has solved the issue. I would recommend anyone with connection problems when using Crystal XI upgrade their ODBC connector to version 3.51.20. Thanks to the MySQL team for the fix.
[17 Sep 2007 5:53] Tonci Grgin
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at

  http://www.mysql.com/downloads/

Explanation: Hi Ziyaad. Just as Craig said, I am too unable to repeat this problem using:
 - MySQL server 5.0.50-PB1046 on WinXP Pro SP2 localhost
 - BO CR XI Patch3, using ODBC (RDO) connection
 - MyODBC 3.51.20GA with just OPTION=1 (no other settings at all)

However one might encounter Error: -2147418113 when trying an OLEDB provider (ADO) which might be related to timing issue described in http://support.microsoft.com/kb/243349. As my box *is* extremely fast that just might be it...