Re: In a Tab Control moving thru Recordset, dirty/undo questions
A clone recordset will absolutely not work. It still touches the same tables. It is not static. You change in the clone it will change in the table. You can do this with transactions, but that is not really the purpose of a transaction. If this is a multiuser database you will lock a large portion of the database for other users while a person has this long running transaction open. I do not understand why you would edit multiple records and then choose to undo them all, but if that makes sense then OK. I would think the only two options are a temp table or a disconnected ado recordset.