It's 2025, and this is still a BUG. I'm not using replication, but I am using an INSERT trigger on the table that generates other new records. My form has an ADODB recordset from SQL Server. A new record is added in the form, and a random record is then displayed that does not even fit the query that the ADODB recordset is based on. Go figure! Work around time.