Training DB, requirements against training

thmsjlmnt3953

Registered User.
Local time
Today, 17:02
Joined
May 20, 2014
Messages
120
Hi,

I have searched however i cant find anything that matches what im looking to do. I already have a db set up on table level for most of what i want

tblemp
tbldepartments
tbltrainingtype (core, additional etc)
tbltrainingskills
tbltraining_records

im struggling now as i need to set up when i input an employee what training they require, then input training they have completed as and when then evaluate the 2 tables to see what is still required if anything?I also need to put a data against training as training expires in a set number of days stored in the trainingskill table
 
I doubt very much that your tables set up to match your business needs.
Do you have a description - clear and simple- of you business and requirements? Do you have a data model? Do you have some test data? Do you have a list of required outputs? Do you have some test scenarios along with the expected result? Have you tested your sample data (and test scenarios) against your data model?

I suggest you show us the plain English description of the business so that we (readers) can understand your situation.
Good luck.
 
Hi,

We have a structure of training specific to departments although some training (core) is shared across all departments. When an employee starts (or changes job) they are given a set of 'required' training which is currently shown by a different colour on an excel sheet. this training is then completed by entering a date - this training expires after a set date and must be redone. This is why im trying to set up a database so i can run a query and report to show training required and also what training is within 30 days of expiring etc

I have sample data on an excel sheet however i guess its the data model and table structure im strugling with?

the outputs id be looking at would be - what training is complete and required per department, per person

the outputs are something i could work on its just how to structure this to begin with
 
You may get some ideas here.

Here is a narrative regarding requirements (from Rogers Access Library). It is an example of defining requirements.

ZYX Laboratories requires an employee tracking database. They want to track information about employees, the employee's job history, and their certifications. Employee information includes first name, middle initial, last name, social security number, address, city, state, zip, home phone, cell phone, email address. Job history would include job title, job description, pay grade, pay range, salary, and date of promotion. For certifications, they want certification type and date achieved.
An employee can have multiple jobs over time, (ie, Analyst, Sr. Analyst, QA Administrator). Employees can also earn certifications necessary for their job.


It helps to keep requirements in focus when building a database.
 

Users who are viewing this thread

Back
Top Bottom