It's clear that the current statement entry solution is a problem, since a) the account_id member of StatementEntry is not accurate when multiple ledger entries contribute to a single statement entry, and b) there is no definitive way to tie StatementEntry to LedgerEntry. The latter isn't too big an issue, but it would certainly be a problem if we allowed transaction editing. If user wanted to change a statement entry account (say from rent to late charge, or from check to cash), there wouldn't be an absolute way to know which ledger entry(ies) to change as well.

Browse Source

git-svn-id: file:///svn-source/pmgr/branches/statement_ledger_entry_tie_20090802@467 97e9348a-65ac-dc4b-aefc-98561f571b83

...

This commit is contained in:

abijah

2009-08-03 02:14:20 +00:00

parent cb716b06b7

commit 4ee9c99e30

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

Diff Content Not Available