I manage the database for a large Christian Men's Chorus. Our annual membership runs in the 300 range from a database with over 1,700 individual records. (I "inherited" this DB from an earlier Membership Chairman who is now long-deceased. The database was originally created using either MS-DOS or Windows 3.1.)
Each year, we need to track the membership fee receipts individually and track the total amount received as we take in current registrations.
We have a non-functioning table that will allow the individual transaction to be entered from a sub-form, but it does not retain all of the receipts. Thus, we have no record of the total receipts in membership fees.
Right now, at the 2/3 point of our recruiting seasons, there are only 35 payment records in that table from the 195 currently registered members who have paid their dues for the year. If we were dealing with a level dues amount, I could look at the number of registrations and multiply by the registration fee amount. That is not the case, as we have one fee for those who are age 22 and younger, and another for those age 23 and up.
It seems logical to use a separate table in this manner. Otherwise, we would have a member table with excessive numbers of fields. However, this idea isn't working and I don't know how to correct it with what I inherited.