Re: Calculated value dilemma

Rainboy <mark.rainbow_at_gmail.com> wrote:

>As keeping historically accurate info is important, 'hard-coding' the
>balance in the table seems to me like it might be the most appropriate
>solution,

Put the balance on the parent table. But also create a method of double checking that number by adding up the individual transactions, telling the user there is a problem, log that problem so they can bring it to your attention at a later date and then fix the balance. Also create this method before even coding the logic to update the balance. Thus you can use it as part of your testing.

Tony

-- 
Tony Toews, Microsoft Access MVP
   Please respond only in the newsgroups so that others can 
read the entire thread of messages.
   Microsoft Access Links, Hints, Tips & Accounting Systems at 
http://www.granite.ab.ca/accsmstr.htm
   Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/