Thinking wider, is there the potential for one certification to require many courses? If so, you'd need to build that in too. My course category suggestion comes from the idea of being able to break courses down ( telephony, software, customer service, company policy, compliance). There would then need to be another junction table for Employees to Events, so as to simulate that many-to-many relationship. It would have information like the CourseID, LocationID, VendorID, and the Start/End Date of the event, as some may occur over several days (e.g. I would create a table for Events, which would therefore be the actual information about a training event. You want to keep your history while the situation changes. Therefore, probably not best to add Role to the employee table as Awesome suggests. 3- the pi chart not showing remaining.Impress the. Would also introduce a table for roles, which would then mean a junction table to simulate the fact that over the lifetime of a term of employment, a person can inhabit multiple sequential roles, whether that be by promotion or simply switching job. Database Template 27202 Access Database Employee Training Plan and Record Templates with Free Examples.
By a few more items I'm thinking of things like Vendor (who is providing the training), it's location (where it is), and perhaps a categorisation of courses. Were I looking to do this, I think I would want to break things down and probably add a few more items.
