Problem with starting structure for DB

[Guest]

I want to create a simple database that does two things:
(1) Keeps track of various students - i.e. Student Number, Name, Phone, etc
(2) Allows tracking of courses that each students takes over a 5 year time
period

Example: New student enrolls so we input his information. 2 Months down the
road, he wants to take a course so we input what the course name is, how
long, location, etc. 2 years from then, same student shows up and wants to
take another course.
The thing is, no course info is stored until the student wants to take that
course. So I have to be able to input it on the fly when he wants to take it.
The course dates may be different, etc.

SO I want to know is should I make two tables (1 for student, 1 for course).
I was going to use a subform to add course info for a particular student, but
it wouldn't work.

Any suggestions?

Thanks,

 

[Joseph Meehan]

I want to create a simple database that does two things:
(1) Keeps track of various students - i.e. Student Number, Name,
Phone, etc (2) Allows tracking of courses that each students takes
over a 5 year time period

Example: New student enrolls so we input his information. 2 Months
down the road, he wants to take a course so we input what the course
name is, how long, location, etc. 2 years from then, same student
shows up and wants to take another course.
The thing is, no course info is stored until the student wants to
take that course. So I have to be able to input it on the fly when he
wants to take it. The course dates may be different, etc.

SO I want to know is should I make two tables (1 for student, 1 for
course). I was going to use a subform to add course info for a
particular student, but it wouldn't work.

Maybe three tables. Student with a unique StudentID filed, a Course
table, with it's own unique CourseID field and an additional Table for the
Dates, (and any other course information that may change.