Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: ODBC error when you use scalar functions to insert timestamp with fractional value
Article ID: 259287 - View products that this article applies to.
This article was previously published under Q259287
When you use ODBC scalar functions with the Microsoft Jet 4.0 OLE DB provider to insert a timestamp that contains a fractional (millisecond) value, the Jet ODBC driver (Odbcjt32.dll) may return the following error message:
Note The Jet 3.51 ODBC driver allows the statement to succeed, and returns SQL_SUCCESS_WITH_INFO and a "Data truncated (timestamp)" message.
[Microsoft][ODBC Microsoft Access Driver] Reserved error (|); there is no message for this error.
The Jet OLE DB driver does not support storage of millisecond values.
To resolve this problem, install the latest Microsoft Jet 4.0 service pack. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/239114/ )How to obtain the latest service pack for the Microsoft Jet 4.0 Database Engine
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This problem was fixed in Jet 4.0 Service Pack 6 (SP6).
Scalar functions are inherent to ODBC, and are used when you need syntax or functionality that cannot be driver-specific. ODBC provides a large number of scalar functions for operations such as string conversion, date and time operations, mathematical functions, and so on.
In this circumstance, the error is generated when you use the ODBC scalar syntax to insert a timestamp that contains a fractional (millisecond) value. For example:
If you use the SQLBindParameter function instead of the scalar syntax, the statement succeeds, and returns SQL_SUCCESS_WITH_INFO and a fractional truncation message.
Article ID: 259287 - Last Review: July 31, 2006 - Revision: 3.6