BUG: RFX_DATE() May Use Incorrect Precision ValueLast reviewed: June 26, 1997Article ID: Q122218 |
The information in this article applies to:
SYMPTOMSUsing the RFX_Date() functions in the Microsoft Foundation Classes fails to work with date/time fields with some ODBC drivers. A general ODBC error or 'invalid precision' error may occur depending upon the ODBC driver. CAUSERFX_Date() calls SQLSetParam() and SQLBindCol() with a precision parameter equal to 23 (sizeof TIMESTAMP_STRUCT). Some ODBC drivers may not use the same precision for a SQL_TIMESTAMP. For example, some ODBC drivers may choose ignore seconds or fractions of a second; in these cases, the precision may be smaller.
RESOLUTIONTo work around this problem, you must re-write the RFX_Date() function and call your new function in your CRecordset's DoFieldExchange(), replacing the RFX_Date() call. In your new RFX_Date() function you will need to:
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available. |
Keywords : kb3rdparty kbprg MfcDatabase kbbuglist
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |