My thoughts exactly. Something keeps telling me that utilizing an extra table for the current balance is the way to go (even though this breaks a normalization rule). I suppose I can keep my data integrity by ensuring I use batch transactions but unfortuantely I am having to do this app with Access and as far as I know it does not support batch transactions through ADO.