The Family table is one of the top-level tables. Below that is the
ClassPayments table, followed by PaymentDetails to show how the payment was
allocated. Even if a Family has just one person taking classes, you still
would want a Detail record to show how the payment is allocated. With
several students in one family it would of course be necessary to do it that
way. In either case, the ClassPayments record is the one used for the
deposit ticket (unless you require a separate check for each student, which
would be unnecessary for the database and inconvenient for the client).

Making some forms makes sense for parts of the database where you are clear
on the design. Good luck. Keep us posted on your progress.

Nomy wrote:
Bruce,
Thanks for the idea, I'll have some time later today to try it. A stand
alone form for non class payments I can see working but I would have to have
another form based on tblpayments with the fields you list and have a
subform based on class enrollment to allocate the payment as a parent could
pay make a single payment for two students in different classes.

I've started to build a couple of small basic forms to test the suggestions
I've received in this newsgroup.

Thanks.
Nancy

Actually, I kind of wish I had not suggested a separate table for
non-class
[quoted text clipped - 60 lines]
Thank you in advanch so much.
Nancy

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/201003/1