Tables: How do I know which relationships to use?

[hesca]

Hello experts. Im trying to create a student database for my guitar students. It basically comprises lists of students under one single subject: guitar lessons. Every student has a schedule: one weekly session at the same date/time every week.
So, here´s my question: How do I create a form that shows information from several tables without relational errors?

I want to create a form with information from 3 different tables, all of which contain autonumber primary keys:

Table 1: Registered: contains the names of the registered students. Fields: StudentName, schedule, teacher, registering date
Table 2. Schedule change: contains the schedule changes for a specific person. I.E. Changing from Monday 4pm to Tuesday 3pm. Fields: studentName, old schedule, new schedule, change date
Table 3. Free sessions: all justified absences entitle the student to get a free session. Fields: StudentName, Absent date, free session date and time

So, I want to show the information for single records on this form: make it contain the student´s details from the "registered" table and also their history of free sessions and schedule changes. So Im creating "one to many" relationships between the primary keys and the name fields, in order to create the logic of "every student has many free sessions" and "every student has many schedule changes".

When I create the form and add tables #2 and #3, the following happens:
a) The existing entries show on table 3.
b) table 2 shows empty even when it contains entries under that student name
c) When I try to manipulate either table the following error pops:



"The changes you requested to the table were not successful because they would create duplicate values in the index, primary key or relationship. Change the data in the fields that contain duplicate data, remove index, or redefine the index to permit duplicate entries and try again"

What am I doing wrong? Any suggestions?
What kind of relationships do you recommend between which fields?

[rpeare]

You'll want to look at using subforms for your subsets of data. Base the main form on the client, then have two subforms, one to their schedule, one to their free sessions, link both subforms to the main from via the studentID.

Once you have this set up you can edit the student's information in the subforms and on the main form individually.