| Bug #23910 | MyODBC causes crash in Crystal Reports when using connection option=3147779 | ||
|---|---|---|---|
| Submitted: | 3 Nov 2006 2:36 | Modified: | 29 Nov 2006 13:55 |
| Reporter: | Matthew Montgomery | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
| Version: | 3.51 | OS: | Windows (Windows) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | MyODBC, stored procedure | ||
[29 Nov 2006 13:55]
Tonci Grgin
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.
If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at
http://dev.mysql.com/doc/en/installing-source.html
Explanation: Can't repeat with 3.51.13 and CR XI
Description: Crystal Reports fails with error when connecting to MySQL using MyODBC and the connection option=3147779 (1 + 2 + 2048 + 1048576 + 2097152) 1 Don't Optimized Column Width 2 Return Matching Rows 2048 Use Compressed Protocol 1048576 Don't Cache Result (forward only cursors) 2097152 Force Use Of Forward Only Cursors Error messages state: crw32.exe - Application Error: 'The instruction at "0x07iiee8c" referenced memory at "0x0000037c". The memory could not be "read".' Visual C++: 'Unhandled exception in crw32.exec (MYODBC.DLL) 0xC0000005: Access Violation.' How to repeat: Connection String: DRIVER={MySQL ODBC 3.51 Driver};SERVER=localhost;DATABASE=xxx;USER=xxx;password=xxx;option=3147779