The information in this article applies to:
SYMPTOMS
Opening a recordset as an append-only dynaset leads to an internal
application error when Update() is called to commit an AddNew(). A
CDBException is thrown, and the following error is displayed in the
output window of the debugger (DB tracing enabled): In Visual C++ 2.x using the Microsoft Access 2.0 driver:
CAUSE
Due to a bug in the MFC code, specifying that a recordset be opened as
append-only results in its concurrency being set to read-only. While the
concurrency is not checked for snapshots, it must be consistent in dynasets
with operations performed on the datasource. RESOLUTIONOpening a recordset as append-only has very limited benefits, so to work around the problem, don't use it. The only real benefit to setting a recordset to append-only is to inhibit you from calling Edit() on the recordset. STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This problem was corrected in Visual C++ version 4.0 but has not been fixed in the 16-bit version of the compiler. We will post new information here in the Knowledge Base as it becomes available. Additional query words: 1.51 2.51 1.52 2.52 2.00 3.00 2.10 3.10 2.20 3.20
Keywords : kbDatabase kbMFC kbODBC kbVC |
Last Reviewed: July 26, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |