structure

[rivet]

1 contact table (contact ID)

1 teacher table (teacher ID)

1 student table (student ID

teacher and students have unique informatio that is stored in thier respective tables, common info (first name, last name, etc.) is stored in the contacts file.

My question is that each student and teacher have stats that are common and unique. Do you think it would be best to create a 'STATS TABLE' that ultimately relate to the contact table?

what are the pros and cons?

[RalphL]

Teacher & Student are sub tables of Contact Therefore Teacher ID = Contact ID and Student ID = Contact ID. These are one to one relationships. Common type data is stored in Contact, Teacher specific data is stored in Teacher and Student specific infromation is stored in Student. A layout for Teacher and a layout for Student both based on Contact used related fields for specific fields from sub tables.

[rivet]

Ralph " Teacher ID = Contact ID and Student ID = Contact ID "

In the above arrangement (one to one) are you having the user create a new contact first and then select if it is a student or a teacher?

Currently I have the user go the to the student or teacher layout (if not already there) and create a new record that would create a relationship in contact once the name had been entered. But this is adding a studentID and TeacherID to the over all project.

Pluse can the one to one handle a contact that is both student and teacher?

thanks - David