Re: Calculated value dilemma

From: Evan Keel <>
Date: Wed, 16 Jul 2008 16:53:00 -0400
Message-ID: <2dtfk.29767$>

"Tony Toews [MVP]" <> wrote in message
> Rainboy <> 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
> 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
> Tony's Microsoft Access Blog -

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

Original text of this message