>I named it "date" to be consistent with the rest of the badly designed tables. :) In the new version I precede everything with a type letter so I avoid that. I went with note1 and note2 because there's always exactly 2 notes, written by the computer, not the user, of a specific size.
>
>I don't need a paid field seperate from the amount field because the pc table contains both payments and trips. The trips have a positive amount, the payments a negatve amount.
>
>I appreciate your thought,
>
Michelle,

You are asking for account aging, but you don't track payments against the transactions. This is like saying "I'm hungry but I don't feel like eating." You can't win.

If you need to age accounts receivable then you need to keep invoices their dates, their original amounts, and their current balance. You need to apply payments against those invoices. Payments should be in their own table, perhaps named Payments.

Theproblema you are having are related to the data design. You must go back and rethink the nature of the information you are recording. There are trips, people pay for these trips, people want a statement every month showing them what they owe, and very likely what they owe it for. You want to kick them in the but if they don't pay, so you want to show them how long ago they took the trip that they haven't paid for.

To do this you need a data design that will record the required information. You need a customer table to know who the peole are, you need a trips table to know what trips have been taken by whom and to keep track of whether or not the trip has been paid, you need a payments table to record each payment received and you need to apply that payment against a trip or even more than one trip.

You need to be able to calculate balances for date ranges. To do this you need data for each trip with the date and the amount still left unpaid. Carrying around calculated balances will be a downfall of the system. It will get out of synch and you won't have the original detail to reconstruct it. You will lose revenue and not even know it.