I know I am probably making you pull your hair out
Here are the tables:
ADVISOR: CENTER INSTRUCTOR
Advisor ID Center ID Instructor ID
Advisor FN Center Name Instructor FN
Advisor LN Center Cycle Instructor LN
Center Area Type
AdvisorID ContactID
LocationID
CONTACT COURSE LOCATION
Contact ID Course ID Location ID
Contact FN Semester Location Name
Contact LN Course NO Location Address
Contact Address CRN Location City
Contact City Section NO Location State
Contact State Course Title Location Zip
Contact Zip Dates1 Location Phone
Contact Phone Dates2 Location Time Zone
Contact Email Dates3
Contact SIN Dates4
Dates5
Text 1
Text 2
Text 3
InstructorID
LocationID
Ok... several comments.
Your Center table has AdvisorID and LocationID fields. Are these filled in, or
are they null? My guess is that they're null, and that the advisor and
location information were not in the Center spreadsheet. If so, you'll
probably want to create a Form based on CENTER, with combo boxes bound to
AdvisorID and LocationID; you can then just go through all the centers
selecting the correct values for these. You should conceal the
(human-meaningless) ID values; for instance, the rowsource of the Advisor
combo might be a query
SELECT [Advisor ID], [Advisor LN] & ", " & [Advisor FN]
FROM ADVISOR
ORDER BY [Advisor LN], [Advisor FN];
Set the combo's column count to 2, and column widths to 0;1 to store the ID
while displaying the name as, e.g., "Evans, Maryanne".
Similarly, you'ld have a Course form with combos for InstructorID and
LocationID.
A couple of suggestions though.... DON'T use blanks in fieldnames, they can
cause trouble down the road and will require that you always use [Square
brackets] around the name in queries and code. They'll work if you do so but
it's an extra hassle. I'd use "Camel Case" - e.g. CourseNo, CourseTitle.
Including the table name in the field name is a matter of style; some folks do
so routinely but I'd just use ID, LocName (not Name, that's a reserved word),
City, State, Zip, Phone, TimeZone as an example. Feel free to include the
name if that works better for you!
But the biggest suggestion is in your Course table. You're "committing
spreadsheet", not surpisingly. Dates1, Dates2, etc. and Text 1/2/3 is
*incorrect design*. Whenever you have repeating fields like this you need
*ANOTHER TABLE* related one to many to this table! If a given Course has five
sessions on five dates, you should have a Sessions table with fields SessionID
(autonumber primary key), CourseID (foreign key to COURSES), SessionDate, and
any information specific to that session. (For instance, I can imagine that a
course might meet at multiple locations for different sessions, in which case
the LocationID should be in the Sessions table rather than in the Course
table). I'm guessing that Text 1/2/3 are textbooks? If so, the same logic
would apply.
John W. Vinson [MVP]
If CourseNo is