Owen said:
I have 15 or so classes set up into one table each class. The fields
are identical but the data will be different. What I need is one page
with a drop down menu that will route the data to the correct table
and one copy of each field in one table.
I'm trying to work it so my users can select the class from the list
enter the data save it and the pick the next class, mean while only
using one page.
Can any one help?
Although I don't know the considerations that went into your table
design, I think your problem would be much alleviated by changing it so
that you have *one* table for all this class data, but with an extra
field that identifies which class a particular record belongs to.
Normally you would also have a separate table of Classes, with one
record for each class, and the primary key of this table would be the
same ClassID or ClassName that you use in the first table.
To elaborate this a bit further, if you were trying to represent
classes, students, and the students enrolled in each class, then you
might have tables like these:
Classes
--------
ClassID (primary key)
ClassDescription
ClassDay
ClassTime
Intructor
Students
---------
StudentID (primary key)
FirstName
MiddleName
LastName
ClassesStudents
-----------------
ClassID (foreign key: Classes)
StudentID (foreign key: Students)
You could then have a form based on Classes, with a combo box that could
be used to move the form to the record for a particular class. On that
form you'd have a continuous subform based on ClassesStudents, linked to
the main form by the ClassID field. The subform would let you view,
add, and delete students from the roster for the class displayed on the
main form.
Of course, this may well not be the situation you're trying to model. I
hope, though, that it gives you the general idea.
