I think the major issue is the set up of the relationship.

One client can have many invoices (1:M)
One client can have many payment plans (1:M)
One invoice can have only one payment plan (1:1)
One client can have many classes (1:M)
One class can have many clients (1:M)
One trainer can have many classes (1:M)
One class can have many trainers (1:M)


June7 wrote:
If the query works then build a report to output the results, not save to a
table. Basic principle of relational database design, Save Raw Data,
Calculate in Report.

I'm building a database for my personal training business, and currently I
ran into a huge pickle and don't know how to bite it. My problem is this, a
[quoted text clipped - 20 lines]
The query does all the calculations but I'm stuck as far as moving the
information into an account table or such.

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