View Single Post
  #6  
Old November 11th, 2005, 05:59 PM
tina
external usenet poster
 
Posts: n/a
Default Is Access even the right idea?

i noticed that in some cases primary/foreign key pairs did not have matching
data types. and in a few cases, you did not use a Lookup table's primary key
as the foreign key in another table - instead, you used another field from
the Lookup table. take a look at the following to compare with your listed
table/fields setup. (note that i didn't really analyze the table design,
just addresses the keys issues.)

ConcentrationLookup
ConcentrationID (primary key - Autonumber)
ConcentrationTitle - text

CourseLookup
CourseID (primary key - Autonumber)
CourseNumber - text

ConcentrationCourses
ConcentrationID (foreign key from ConcentrationLookup - Long Integer)
CourseID (foreign key from CourseLookup - Long Integer)

EmailLookup
EmailTypeID (primary key - Autonumber)
EmailType - text

HomeSchoolLookup
HomeSchoolID (primary key - Autonumber)
HomeSchool - text

PhoneNumbers
PhoneID (primary key - Autonumber)
StudentID (foreign key from Students - Text)
PhoneTypeID (foreign key from PhoneTypeLookup - Long Integer)
PhoneNumber - text

PhoneTypeLookup
PhoneTypeID (primary key - Autonumber)
PhoneType - text

ProgramData
ProgramID (primary key - Text)
StudentID (foreign key from Students - Text)
DateAdmitted - date/time
DateUpdated - date/time
ConcentrationID (foreign key from ConcentrationLookup - Long Integer)
StatusID (foreign key from StatusLookup - Text)
Comment - memo

SemesterLookup
SemesterID (primary key - Autonumber)
SemesterStartDate - date/time
Semester - text

StatusLookup
StatusID (primary key - Text)
StatusType - text

Students
StudentID (primary key - Text)
FirstName - text
MiddleInitial - text
LastName - text
ProgramID (foreign key - Text)
ConcentrationID (foreign key - Long Integer)
HomeSchoolID (foreign key - Long Integer)
Address1 - text
Address2 - text
City - text
State - text
ZipCode - text
Advisor - text
DateUpdated - date/time

StudentPhones
PhoneID (primary key - Autonumber)
StudentID (foreign key - Text)
PhoneTypeID (foreign key - Long Integer)
PhoneNumber - text

StudentEmail
EmailID (primary key - Autonumber)
StudentID (foreign key - Text)
EmailTypeID (foreign key - Long Integer)
EmailAddress - memo

CourseStatusLookup
CourseStatusID (primary key - Autonumber)
CourseStatus - text

hth


"BMB" wrote in message
...
Thank you for the suggestions. They have helped. I think that I have all
the tables constructed (maybe), but the assimilation part is proving more
complicated than I had thought. As I establish relationships between the
tables, I seem to get less functionality and information retention than
before. The following is my table structure. Further assistance would be
greatly appreciated.

Table structure-----

ConcentrationLookup
ConcentrationID (key) - autonumber
ConcentrationTitle - text
CourseLookup
CourseID (key) - autonumber
CourseNumber - text
CourseToConcentration
ConcentrationID - autonumber
CourseID - text
EmailLookup
EmailTypeID (key) - autonumber
EmailType - text
HomeSchoolLookup
HomeSchoolID (key) - autonumber
HomeSchool - text
PhoneNumbers
PhoneID (key) - autonumber
StudentID - text
PhoneTypeID - text
PhoneNumber - text
PhoneTypeLookup
PhoneTypeID (key) - autonumber
PhoneType - text
ProgramData
ProgramID (key) - text
StudentID - text
DateAdmitted - date/time
DateUpdated - date/time
ConcentrationID - text
StatusID - text
Comment - memo
SemesterLookup
SemesterID (key) - autonumber
SemesterStartDate - date/time
Semester - text
StatusLookup
StatusID (key) - text
StatusType - text
StudentDemographics
StudentID (key) - text
FirstName - text
MiddleInitial - text
LastName - text
ProgramID - text
ConcentrationTitle - text
HomeSchool - text
Address1 - text
Address2 - text
City - text
State - text
ZipCode - text
PhoneType - number
PhoneNumber - text
EmailType - number
EmailAddress - memo
Advisor - text
DateUpdated - date/time
StudentEmail
EmailID (key) - text
StudentID - text
EmailTypeID - text
EmailAddress - memo
CourseStatusLookup
CourseStatusID - autonumber
CourseStatus - text

The following information may be necessary: ProgramID is a four-digit

number
that we assign to students as they apply for our program as a method of
internal tracking; all courses are available each semester; there are 7
course requirements that are common to all 5 concentrations.

I would like to create a tabbed form that contains one tab for basic

student
information and subsequent tabs that contain scheduling data for the
requisite courses based upon the student's chosen concentration (i.e., one
tab for each concentration, but only the appropriate tab accessible based

on
the "Concentration" selection on tab 1).

If you're still even reading this, thanks.