Current recordset does not support updating vba
The simplest reports every 100th record in the loop like this: If you use Seek or one of the Find methods (Find First, Find Last, Find Next, Find Previous), and do not test No Match, your code will appear to work until you strike a case where the find failed.Always test for No Match after using Seek or a Find method.Example: It is poor programming to open anything without explicitly closing it. Short of pressing Ctrl Alt Del, you may find that Access will not quit if recordsets or other objects are not closed and dereferenced.Always close recordsets and set objects to Nothing in the error recovery of your procedure.When you Open Recordset() on a local table, it defaults to a Table type (db Open Table.) The Table type has different methods (e.g.Seek instead of Find First), but it cannot be used with attached tables.In ADO, this object is the most important and the one used most often to manipulate data from a database.
The DAO and ADO libraries both have a Recordset object, but with different methods, properties, and options.See Solving Problems with Library References for details. To ensure your code works reliably: There are different types of DAO recordset, with different methods.When you Open Recordset() on a query or attached table, Access defaults to a Dynaset type (db Open Dynaset).Record Count will always be at least 1 if records exist, so there is no need to Move Last if you only want to know if you have records to work with.A Move Next may take you to the end of the recordset (EOF) or a Move Previous to the beginning of the recordset (BOF).
DAO is the native Access library (what Access itself uses), whereas ADO is a more generic library (now superseded by the vastly different ADO.