I have a VBA procedure the correct functionality of which depends upon the "<recordset>.movelast" method accessing, consistently, the record most recently added to the recordset (I.e. that new records are added to the end of the recordset and that the order of records in the recordset is fixed.). The procedure did work satisfactorily for some time but has recently failed. I recall that the relational model requires that the order of records in a table be undefined; is this the case in Access and if so what does "movelast" do?