Y
yeshwant
wrewr
-----Original Message-----
From: Steve Schapel
Posted At: Friday, May 20, 2005 11:40 PM
Posted To: microsoft.public.access
Conversation: Tables and Forms
Subject: Re: Tables and Forms
John,
From your description, there is a one-to-many relationship between
Students and Enrolments. This should be reflected in your table
structure. There is also a one-to-many relationship between Courses and
Enrolments. Therefore, you need at least 3 tables: Courses, Students,
Enrolments. The Enrolments table will need a Foreign Key field to
relate it to both of the other two tables. For example, it might have
fields something like this...
EnrolmentID
StudentID
CourseCode
EnrolmentDate
Therefore, John Smith's details (name, address, etc) only get entered
once into the database, and every time he enrols in a course, all you
need is to get his StudentID into the Enrolments table.
Not a complete answer, but hopefully it will help point you in a useful
direction.
-----Original Message-----
From: Steve Schapel
Posted At: Friday, May 20, 2005 11:40 PM
Posted To: microsoft.public.access
Conversation: Tables and Forms
Subject: Re: Tables and Forms
John,
From your description, there is a one-to-many relationship between
Students and Enrolments. This should be reflected in your table
structure. There is also a one-to-many relationship between Courses and
Enrolments. Therefore, you need at least 3 tables: Courses, Students,
Enrolments. The Enrolments table will need a Foreign Key field to
relate it to both of the other two tables. For example, it might have
fields something like this...
EnrolmentID
StudentID
CourseCode
EnrolmentDate
Therefore, John Smith's details (name, address, etc) only get entered
once into the database, and every time he enrols in a course, all you
need is to get his StudentID into the Enrolments table.
Not a complete answer, but hopefully it will help point you in a useful
direction.