Seems as if you want to get the information into 1 database you will have
quite a lot of work.
I think you need a table of Professors ProfID & ProfName etc
A Table of Courses CourseID CourseName, CourseDate etc
A JoinCourseProf CourceID & ProfID.
That way a professor can be involved in lots of different courses, and
equally a course can be tutored by lots of professors.
You then want Student table, Yes you guessed StudentID, StudentName,
StudentEMail.
A JoinStudentCourse - StudentID & CourseID
An Exam (Test) Table ExamID, ExamName
and finally a JoinStudentExam StudentID , ExamID, ExamDate, Marks
So a Student Form could show 2 Subforms, 1 listing Course they are on and 1
listing Exams and their results
A Course form would have 2 subforms 1 listing Profs involved with that
course, and 1 listing Students.
Needless to say eventually you will need to enforce referential integrety
between the tables.
With a bit of luck if this information is in your current tables, you should
be able to use append queries with temporary links between say ProfsNames to
get the right information into the new tables
HTH
Phil
"David" <th****@cablespeed.com> wrote in message
news:11**********************@c13g2000cwb.googlegr oups.com...
Originaly there were two seperate databases. One was for Entering in
Test that a professor sent to our office and one for when a student
came to take a test for a professor. Well I was thinking I could link
the table from the Test Db to the Sign In DB since the Test Database
already has alot of the info for the sign in database. That way we
could retrieve this information without us having to type it in for
every student. The Test Database and Sign in Database both have fields
for Professor, Course, and Mail. In the Sign In form the student
selects from the combo list which cascade to limit the data(The list is
based of the Test Db, but the control source is in the sign In db. For
the proctor form, this is where I need the mail fields to pull from the
test db.