Recordset error "too many transactions"

[TheSmileyCoder]

Yes, I believe so.

There is also something called a batchupdate, but I can't remember how exactly that works at the moment.

[reginaldmerritt]

Live an learn. I'll make sure i add .update from now on.

Sorry we went all around the houses there.

[TheSmileyCoder]

Not your fault :P Just glad you found a solution to your problem.

[NeoPa]

Does this need to be done every time a recordset is edited?

Yes.

Both rs.New & rs.Edit put the database into an edit and therefore create a transaction. This is only closed (submitted to the database) when rs.Update is called. Many changes can be made between the two lines, but none is committed (saved) until the rs.Update tells it to.

In the mean-time, Access needs to keep a record of all the proposed changes. You can imagine how this could build up in your process if the rs.Update is never called.

I suggest a quick read of the relevant Help page (click on the .Edit line and press F1) would considerably help your understanding. They explain it better than I can.