Bug #29888 | Crystal wizard throws error on including tables | ||
---|---|---|---|
Submitted: | 19 Jul 2007 1:15 | Modified: | 26 Jul 2007 14:28 |
Reporter: | Jared S (Silver Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S1 (Critical) |
Version: | 3.51.17 | OS: | Windows (Vista) |
Assigned to: | Jim Winstead | CPU Architecture: | Any |
Tags: | Connection, crystal, SQLColumns, wizard |
[19 Jul 2007 1:15]
Jared S
[19 Jul 2007 1:16]
Jared S
ErrMsgBox
Attachment: CrystalErr.jpg (image/pjpeg, text), 21.90 KiB.
[19 Jul 2007 1:17]
Jared S
See HY000 error
Attachment: SQL.LOG (application/octet-stream, text), 72.99 KiB.
[19 Jul 2007 20:14]
Jim Winstead
Fix problems with SQLColumns() when catalog is specified
Attachment: bug29888.patch (text/plain), 2.31 KiB.
[23 Jul 2007 22:55]
Jared S
Hi Jim, did you have time to 'preview' simple crystal report, as alot of crystal bugs are slipping through current releases.
[25 Jul 2007 19:45]
Matt Ashley
Jim, I looked at your patch for this issue but don't know how to apply it. Don't know much about compiling source code. Do you know which release of the odbc driver this will be released in and when it is do out?
[25 Jul 2007 20:50]
Jim Winstead
The fix for this bug has been committed, and will be included in 3.51.18.
[25 Jul 2007 22:39]
Matt Ashley
Thanks Jim. Do you know a time frame when 3.51.18 will be released?
[26 Jul 2007 14:28]
MC Brown
A note has been added to the 3.51.18 changelog: Getting table metadata (through the SQLColumns() would fail, returning a bad table definition to calling applications.