Thread: Dance Classes
View Single Post
  #14  
Old February 25th, 2010, 05:59 PM posted to microsoft.public.access.tablesdbdesign
BruceM via AccessMonster.com
external usenet poster
 
Posts: 448
Default Dance Classes

As I understand, a payment is made by the person identified in the Family
table. It may be for more than one student, in which case it is for a larger
amount than is needed for either of the students individually.
tblClassPayment should have a CheckAmount field in addition to CheckNum, etc.,
and any link to DepositDetail should be by way of tblClassPayment, as you
will be depositing the entire check amount, not the amount attributable to
each student.

How much detail do you need in the DepositDetail records? Do you want Family
information, Student information, bank information, check number, or what
exactly? If you need that type of information you would link to the ID field
only, and use a query to show the rest of the data. At the same time you may
need fields to store details about non-class payments. A separate table to
list such income (which is different than a separate Deposit table) may be
the best way to proceed, as you would be able to store a single ID field in
the DepositDetail record. That said, I don't see a structural problem with
leaving the ID field blank.

Remember that your record of payment received is already in the
tblClassPayment, so by associating a DepositDetail record with a ClassPayment
record you are storing only the information of when a specific check was
deposited, which may be more Deposit information than you need. It can be
done, but it may be quite a bit of work for minimal gain. However, I think
in any case the DepositDetail record should have a Comments field or some
such.


Nomy wrote:
Bruce and Steve,

Thank you both so much for your valued assistance. Sorry for the delay in
answering but had to leave town for a family matter unexpectedly, and I
didn't have access to a computer and have just returned. I've read the
posts and there are several interesting possibilities.

All the suggestions were excellent and I think it would be good to be able
to track deposits of class payments and non class deposits but I don't think
I need two sets of deposit tables. There is only one bank account and I
think it would be easier to track back if all deposits were together and be
able to identify what kind of deposit it was in addition to cash or check.

If I had a field in the deposit detail table called ClassPaymentDetailID as
Steve suggested in his first answer, then that field would link back to a
class payment after appending the data. Correct? I would then enter the
non class deposits manually as Bruce suggested.

The other side of this coin would be the ClassPaymentDetailID field would be
empty for deposit details that were not class payments. Do either of you
see this as a problem?

I'm going to read through everything again and think it all through very
carefully. I'm not exactly new to access but have been away from it for a
while and have to brush up on a lot. I have never used the VBA code to add
new recordsets so I have my work cut out for me.

I'm excited about doing this project and eager to continue. This newsgroup
is an awesome tool.

Thank you both again for all the help.
Nancy

I'll wait to see what the OP has to say. If there is a business need to
separate class payments and non-class income, that is one thing, but I am

[quoted text clipped - 25 lines]
Thank you in advanch so much.
Nancy


--
Message posted via http://www.accessmonster.com