Check Printing - Addresses
warlord at MIT.EDU
Fri Jul 6 10:32:07 EDT 2007
Andrew Sackville-West <ajswest at mindspring.com> writes:
>> I still don't see why it matters. Something like the Payee should be
>> tied to the Description, which is part of the Transaction object, not
>> the Split object. So it doesn't matter which is the "primary Split"
>> in order to add ancillary information to the Transaction.
> I thought the business stuff was tied in through the a/p a/r register
> and the owner information. And that getting to that split would get
> you to that information thus eliminiating the need for some other
> "payees" database as that information already exists in the business
Nope, the business stuff isn't in the registers at all. This is
why you NEED to use the Invoice and "Process Payment" functions
through the menus and NOT use the registers.. The registers have
no clue about the business features.
Now, it might be worth it to add a "contact database" and migrate
the customer and vendor list to a common "contacts DB". And then
we could tie the check-printing and register payees into the
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord at MIT.EDU PGP key available
More information about the gnucash-devel