Re: Calculated value dilemma

"Tony Toews [MVP]" <ttoews_at_telusplanet.net> wrote in message news:ijls74hco85ernlcubpedveu1cm6dblmi0_at_4ax.com...
> 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/

Can't wait to see the responses to this. Received on Wed Jul 16 2008 - 22:53:00 CEST