I am creating a table that keeps track of safety/training certificates for our employees. There are up to 20-30 different trainings our employees get. Most of these have issue and expiration dates. I was thinking that creating a table with Yes/No fields for each training, so that there is only one record per employee that just keeps getting updated instead of many records of the same user for different trainings. However, like stated above, I would already have 20+ fields in this table for the trainings alone. I wouldn't want to add an Issue and Expiration field for each one, that would triple the amount of fields I have.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
kpcollier
I am creating a table that keeps track of safety/training certificates for our employees. There are up to 20-30 different trainings our employees get. Most of these have issue and expiration dates. I was thinking that creating a table with Yes/No fields for each training, so that there is only one record per employee that just keeps getting updated instead of many records of the same user for different trainings. However, like stated above, I would already have 20+ fields in this table for the trainings alone. I wouldn't want to add an Issue and Expiration field for each one, that would triple the amount of fields I have.
Any work around for this?
Link to comment
Share on other sites
8 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.