On May 7, 5:06*am, Paul H <goo...@comcraft.freeserve.co.ukwrote:
Quote:
I have a transactions table and a balance table that look something
like this:
>
tblTransactions
TransactionID (PK Autonumber)
ClientID
TransactionDate
TransactionAmount (currency field, values must be >0)
CRDR (indicates whether the transaction is a (credit or debit)
StatementDate (Date stamp applied when the “Statement” report is run)
>
tblAccountBalance (no PK in this table)
ClientID
AccountBalance (currency field can be >0 or <0)
BalanceDate (Date stamp applied when the “Statement” report is run)
>
My goal is to have a report that shows the following:
>
Opening balance
Transactions for this period
Closing balance
>
When I run the report, I apply a date stamp to the “StatementDate”
field of each row in tblTransactions where the StatementDate is either
null or within the statement period. That works fine.
>
But I am getting mixed up with when to apply the date stamp to the
“BalanceDate” field in tblAccountBalance. Rather than go into detail
about all of the permutations that are sloshing around in my head, can
someone reassure me that my approach thus far is correct (or at least
workable) and give me a nudge in the right direction.
>
Thanks
>
Paul
tblBalance is a good idea, allows you to archive transactions after a
period of time by updating the accountBalance with the value of the
archived transactions
but it is not a good design idea to use it as an accumulator of past
invocations of the report
I'm guessing your scenerio is
for clientId 1, the balance is 0
run report which marks some transactions ($1000) with a statement
date
update accountBalance to $1000, balanceDate is ????
one month later run report with $2000 of transactions and mark
another date
update accountBalance to $3000, balanceDate is ???
now what happens when the client wants a statement for the past 2
months ?
how do you rebuild the first statement is the account balance is no
longer 0 ?
now, if you use accountBalance as only the client opening balance,
you'd change the report's opening balance to be accountBalance +
sum(any transactions prior to the statement date), so
for clientId 1, the balance is 0 + 0
run report which marks some transactions ($1000) with a statement
date
one month later run report with $2000 of transactions and mark
another date
opening balance is 0 + 1000 (sum of prior transactions)
to rebuild first statement, opening balance is 0, you'd select all
transactions
where the statement date <= a 'reprint' date
ditto for a statement that spans multiple months
three years from now, you'd have a function that moves transactions to
an archive table, or deletes if you don't care to about the details
and updates the accountBalance to say $100,000
and sets the balanceDate to the archive date
now the next statement you create
for clientId 1, the balance is $100,000 + 0
run report which marks some transactions ($2500) with a statement
date
etc
