Bug #4833 WinXP ODBC driver 3.51.08 hangs in Crystal Rpts Pro 10
Submitted: 30 Jul 2004 18:40 Modified: 1 Dec 2005 12:24
Reporter: Matthew LHeureux Email Updates:
Status: Closed Impact on me:
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51.08/3.51.10 OS:Windows (WinXP SP1)
Assigned to: CPU Architecture:Any

[30 Jul 2004 18:40] Matthew LHeureux
The WinXP ODBC Connector driver 3.51.08 appears to be incompatible with Crystal Reports Pro 10 (to some degree).  In Crystal, as I would drag tables to the workspace, I would run out of virtual memory and eventually my PC would crash.  I backed out the 3.51.08 driver and install the older 3.51.06 and this resolved the issue.  With 3.51.08, dragging the table would take 15-20 minutes until the desktop would crash.  With the 3.51.06 driver, it takes a millesecond without issue.

How to repeat:
Drag a table into the report writing workspace.  I'm not talking about browsing the table, just simply selecting it as a table that you will work with.

Suggested fix:
I needed to go back to v3.51.06 of the driver.
[13 Dec 2004 16:43] MySQL Verification Team
Thank you for the bug report.
[11 Feb 2005 19:10] Peter Harvey
I think this was 'resolved' by forcing ODBC version to v3 in SQLAllocConnect. But this fix has been rolled back as it causes problems with MS Access which really want v2.
[19 May 2005 19:21] Muhammad Meghji
I had a similar problem to this on Crystal Reports Pro 10 using the ODBC Driver 3.51.08. 

Once I setup the connection through with Crystal Reports - I wanted to drag and drop relevant fields from the Database to the Report itself in the report designer. This action always crashed the report writer.

Instead of downgrading to v3.51.06 of the ODBC driver, I updated the driver to the latest one v3.51.11. Unfortunately, the same thing happened. So I unistalled this version and isntalled v3.51.06. Again, unfortunately, this behaviour continued. I am now not certain which driver would work with the Crystal Reports Pro 10. Does anyone have a solution do this? 


[23 May 2005 16:18] Muhammad Meghji

I continued to play with this problem until I found a fix. Unfortunately, unistalling a version of MyODBC is not sufficient to stop this crash. Instead:

(1) Unistall th version of myODBC that crashes Crystal Reports.
(2) Key step: Go to your Windows/System32 folder and Delete all files begining with myodbc* (there should be about 4 or 5)
(3) Now reinstall the version of myODBC that works with Crystal reports v3.51.06

Hope this helps someone.

Muhammad Meghji
[26 Nov 2005 9:43] Valeriy Kravchuk
Please, try to repeat the problem you described with the latest 3.51.12 version of the ODBC driver. Inform about the results.
[28 Nov 2005 15:26] Matthew LHeureux
The problem no longer exists when using 3.51.11 or higher.
[1 Dec 2005 12:24] Valeriy Kravchuk
Closed as solved by 3.51.11 or newer versions, as reported in the last comment.