brialex
Leslie is correct in that storing calculations does break the third rule on normalization. The idea with relational tables is remove redundancies, thus simplify maintenance.
However, I realize that with accounting, balances are useful. Moreover, it can save a heck of a lot of CPU time if you have 10,000's of transactions.
Although I have seen a balance on the G/L master record, a better solution from my perspective, is to have a monthly balance table.
As part of the month-end process, the balance table is updated for the posted month for each account. Now, when you want to now the current balance, you retrieve the balance for the previous month-end, and then run SUM calcualtion query for the current month.
This can be done, but you will need to create a centralized posting module, and do a heck of a lot of maintenance.
Have you considered purchasing an accounting applicaiton such as Quicken or MYOB or PeachTree, etc. For $50 to $200, you can save yourself a heck of a lot grief.
Richard