Windows 7 32bit 
Access 2010 32bit
OK then, in that case you probably can do away with those two tables. See below for how you might deal with access levels.
Actually TrainerCompanyID and LineLeaderID are exactly the same as EmployeeID,
In that case, no, you don't need a training type. Identifying an employee as a trainer would suffice.Trainers in my company can give generic training to all employees, in fact that's all they allowed to do, anything more difficult would require engineers to step in so if 1 or more trainers are absent others can fill in. Do I still have to add training type to trainers?
You can handle that with the LineLeader field in the tblEmployee (see post #11 above) together with permissions.According to Company's policy only line leaders can request a training,
For permissions - do you have, or will you have, a Login? If so, you can determine what the logged in user is allowed to do by checking those YesNo fields in the Employee table. Later on, if you find you need additional permission levels (e.g. for reports), you could put all the permissions into a new tblPermission, without having to change tblEmployee all the time.
Reply With Quote
