Depending on the search criteria for the recordset and what changes were made, the record might not be included in the search results after the requery.

Any changes were immediate, it would be preferable to give the user the opportunity to not save the changes if they make a mistake.

We were also experiencing issues with the backend suddenly in "inconsistent state", this was always occurring immediately after updating a record, sometimes Access was not able to repair it. I wasn't sure if multiple users having same records open/editable in a recordset was part of the issue, so changed it to read-only and added the db.execute method for updating.