Bug #21398 ADO incorrectly reporting DECIMAL field type through MySQL ODBC
Submitted: 1 Aug 2006 17:58 Modified: 9 Aug 2006 15:34
Reporter: Brian Marks Email Updates:
Status: Not a Bug Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version:3.51.12 OS:Windows (Windows XP)
Assigned to: CPU Architecture:Any
Tags: ADO, field, MySQL, ODBC, recordset, type

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[2 Aug 2006 19:36] Miguel Solorzano
Access displaying decimal data type

Attachment: bug21398.PNG (image/png, text), 15.24 KiB.

[8 Aug 2006 15:24] Tonci Grgin
C++ test case

Attachment: bug21398.cpp (text/x-c++), 4.90 KiB.

[8 Aug 2006 15:58] Tonci Grgin
VB script

Attachment: bug21398.vbs (application/octet-stream, text), 1.62 KiB.

[8 Aug 2006 15:58] Tonci Grgin
VB script result

Attachment: 21398.jpg (image/jpeg, text), 35.56 KiB.

[8 Aug 2006 17:34] Brian Marks
Output from script on user's machine

Attachment: mysqlerr.JPG (image/pjpeg, text), 7.76 KiB.

[9 Aug 2006 13:48] Tonci Grgin
Files with rellevant SW versions

Attachment: MDACfiles.zip (application/x-zip-compressed, text), 3.43 KiB.

[9 Aug 2006 13:51] Tonci Grgin
New C++ test case using unicode function SQLDescribeColW

Attachment: bug21398.cpp (text/x-c++), 5.06 KiB.