
Originally Posted by
thekruser
Yes, that is the way I have it, I just left out the third table for ease of understanding the concept. I actually have 3 tables that feed tblTraining, which is the same as you are describing.
Actually you do NOT have it the way ConneXionLost is suggesting. I also agree with that recommendation.
I think that there is a normalization issue that is causing you so much grief.
What you we are recommending is something like this:
Code:
tblPersonal
-PersonalID (PK) - automuberr
-Employee# - indexed and no dups
-LName
-FName
-MI
etc
[code]
tblCourses
-CourseID (PK)
-CourseName << Be careful of reserved keyword!
-Code
-Location
-CourseDescription << Be careful of reserved keyword!
etc
['code]
[code]
tblTrainingStatus
-TrainingStatusID (PK)
-Status (e.g., Active, Pending, Attending, Cancelled, Completed, Failed, etc)
-TrainingStatusDescription
tblTrainingClass
-TrainingClassID (PK)
-CourseID (FK)
-StartDate
-EndDate
tblTrainingClassAttendees
- EmployeeTrainingID (PK)
- TrainingClassID (FK)
- PersonalID (FK)
- TrainingStatusID (FK)
- DateCompleted