If a student can attend many courses and a single course can have many students you have the classic example for the use of a join table or Associative Entity in relational database terminology
Students Attendance/Enrollment Courses
pk_student_id pk_join_id pk_course_id
You need to study a bit... its a basic many to many relaitonship
The main idea is to have an extra table to have 1 to many relationship both times
I am assuming you are familiar with Primary and Foreign Keys
Funny it has the example you are looking for
Simplest way—I assume you have already set up the join table (SignUps) and the relationships to it from both student and course:
1. Create a Value List of all students, using first value studentID, second value studentName, show only second value
2. Create a Value List of all courses, using first value courseID, second value courseName, show only second value
3. Make a portal to the join table on a student layout—in the portal you only need the courseID set up as a popup menu showing the courses value list
4. Make a portal to the join table on a course layout—in the portal you only need the studentID set up as a popup menu showing the students value list
You can then enter courses undertaken by an individual student, and students enrolled i an individual class, from either perspective.
Thanks and I don't see any attachment.
View this discussion in a web browser not as email and you should see the file to download.
Thank you very much.