I seem to remember a discussion which I haven’t relocated yet that recommended NOT to use the RecordSet.Edit/Update and the InsertRecord functions.
Would someone remind me why this might be the case. It seems like it might have been something related to using a SQLite database and then possibly moving to a client/server.
It tends to be slower from my experience. And if it’s within a loop there’s probably a better way of updating the recordset via straight SQL. Otherwise, it uses prepared statements behind the scenes and is safe to use. I don’t see why you would need to change any existing code.
Thanks Bob, have never needed to put one in a loop so that’s not a problem.