Thanks for everyone's advice & comments - an exception index seems the
way to go and Ralph, as ever when I'm setting up a new DP app, your book
will be close at hand :-)
Michael
Ralph Alvy wrote:
Michael,
You can read up on this approach in my book. It has an exhaustive
section on Exception List Indexes, where this approach is outlined.
On Tue, 18 Jul 2006 09:52:10 -0700, Don Friedman
<[EMAIL PROTECTED]> wrote:
Michael - it would seem to me that you'd want to use an exception
index so
that when a payment is made it takes the paid invoice "off" the
unpaid list
while keeping everything else on. That would involve posting a
payment to a
specific invoice, not simply an open balance. It also seems to me
that you'd
want to do this on an invoice-by-invoice basis so that if a customer has
multiple unpaid invoices they would all show, not simply the last
invoice
issued.
Don
On 7/18/06, Michael Iannantuoni <[EMAIL PROTECTED]> wrote:
I'm setting up a database to keep records of payments of advertisers to
our village magazine:
I have a main "Contact" panel linked to a "Payments" panel where the
fields include "Payment-from" and "Payment-to".
We need to keep records of all previous payments so each advertiser
will
have a number of records in the "Payments" panel but I would also like
to set up a system whereby overdue payments are flagged - something
like
"if today - Payment-to is greater than 0 then flag" but I'm not sure
how
to get this to operate on only the last payment record for each
advertiser.
Any help, or different approach, much appreciated.
Michael
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
