I suspect that you are correct in that it will still only take a few seconds to update all of the currencies so maybe it's not a big deal...Bloating may not be much if you clear and write to the same table - or use an external file.Hello experts, I need to update the currency exchange rates in an Access (2010) tab many times a throughout the day.
Not a lot of bloat in the grand scheme of things, especially when the database is going to increase in size anyway due to normal data entry so probably nothing to worry about. You may find that rephrasing your criteria to locate a specific record is faster, especially when working with large recordsets.
The down side is with 120 currencies to update function would run 120 times for each overall currency update process.
Not very efficient but maybe it doesn't matter in the grand scheme of things.
I think a faster recordset method would do something like this: * Instantiate a recordset object against the base table (db Open Table) without any row-limiting criteria * Start a transaction (Begin Trans) * For Each item in your update collection/dictionary, invoke a recordset .
FIND method for the key to the row to be updated, then use rs. Update to change the row * After all your updates, invoke the Commit method to end the transaction.