DOCERR: New Record Not Inserted to the End of Recordset

 Last reviewed: July 2, 1997
Article ID: Q170119
The information in this article applies to:
  • The Microsoft Foundation Classes (MFC) included with: - Microsoft Visual C++, 32-bit Editions, versions 4.2, 5.0 ---------------------------------------------------------------------

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.

Keywords : MfcDAO
Technology : kbMfc
Version : 4.2 5.0
Platform : NT WINDOWS
Issue type : kbdocerr

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.