Paul 18 Mar 2005 It is not necessary to buffer a table for transactions to work. Nevertheless, I usually buffer a table (or use a view), then if a transaction is necessary, put the transaction only around the TABLEUPDATE in order to keep the transaction short. But I'm really guessing here. Am I approaching it in the best manner? What general rules are there for handling buffering and transactions? Also, I occasionally want a transaction to cover changes to several tables, with some calculation done during the process, and even a couple nested transactions. The whole thing could take a few seconds (in a multi-user environment). Is there anything specific I need to look out for? Other than the limit on transaction levels, I mean.