DOC: New Record Not Inserted to the End of Recordset
Article ID: 170119
Article Last Modified on 11/21/2006
APPLIES TO
- Microsoft Foundation Class Library 4.2, when used with:
- Microsoft Visual C++ 4.2 Enterprise Edition
- Microsoft Visual C++ 4.2 Professional Edition
- Microsoft Visual C++ 5.0 Enterprise Edition
- Microsoft Visual C++ 5.0 Professional Edition
This article was previously published under Q170119
SUMMARY
The MFC documentation for CDaoRecordset::AddNew() and the DAO SDK
documentation for the AddNew method state:
The position of the record depends on the type of Recordset:
In a dynaset-type Recordset object, records are inserted at the end of
the recordset, regardless of any sorting or ordering rules that may have
been in effect when the recordset was opened.
The documentation is incorrect. Beginning with Jet 3.0, this behavior is
not guaranteed. The behavior was changed to improve performance as well as
concurrency issues.
To demonstrate the change in behavior, delete a record in a recordset of
300+ records and then call AddNew(). Then, traverse the recordset until you
see where the record has been added. Typically this record will be inserted
in the 253rd record rather than at the end of the recordset.
MORE INFORMATION
If the goal is to make the newly added record the current record, you
should get the bookmark of the last modified record and move to that
bookmark.
This documentation was corrected in Visual C++ version 6.0 for Windows.
Keywords: kbdatabase kbdocerr kbdocfix KB170119