FIX: Trailing Zeros Truncated with ADO OLEDB Provider for ODBC

• Microsoft OLE DB Provider for ODBC, version 2.0

SYMPTOMS

When using the OLEDB provider for ODBC, numeric data types returned from the database are returned with the trailing zeros to the left of the decimal place truncated.

For example:

100 would be returned as 1.

2200 would be returned as 22.

CAUSE

This data truncation is a result of a problem with the translation of the ODBC data type to its equivalent OLEDB data type. This problem occurs when the ODBC driver being used returns a negative value for the scale element of the SQL_C_NUMERIC structure.

RESOLUTION

This has been confirmed to be a bug in the MDAC components. There is a fix for this problem which is discussed in the STATUS section of this article. In addition to this fix, there are several other workarounds to this problem:

• Modify the query that brings back the numeric type so that the numeric type is converted to strings before returning. For example, "SELECT convert(char(10),field1) FROM TABLENAME."



• Use the ADO client cursor library instead. This can be done by specifying Connection.CursorLocation = adUseClient.



• Use the native OLEDB provider for the database, if one is available.

STATUS

This problem has been fixed in Microsoft ActiveX Data Objects versions 2.5 and later.

REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

Q195470 PRB: MDAC 2.0 ODBC Requirements for Numeric Fields

Additional query words:

Keywords : kb3rdparty kbDatabase kbMDAC kbOLEDB kbOLEDB210bug kbOLEDB210fix kbGrpASP kbDSupport kbMDAC210SP2fix
Version : WINDOWS:2.0
Platform : WINDOWS
Issue type : kbbug