I am working on my final project for school, and attempting to fulfill the criteria that states, "Use as many Access tools as possible in your database."
I created a table for employees of a fictional airline. I want to track their certifications. Of course, employees could have many roles, and many certifications: college degree, airport certification, safety and security, pilot licenses, etc. I thought this would be a good time to add a multivalue field to my tblEmployee table. I also decided to be adventurous, and use more than 1 column, even though I don't know if that actually works in this context and it isn't in my textbook. Now, I have 4 columns and 18 fields, and I'm wondering if this is a good idea? I'm especially wondering as the next window in the Lookup Wizard asks me which column I want to use that uniquely IDs the row, so it can store that value in my database. On one hand, a sub-table might make more sense. On the other, my grade depends on using as many Access tools as I can.
Any suggestions?
I created a table for employees of a fictional airline. I want to track their certifications. Of course, employees could have many roles, and many certifications: college degree, airport certification, safety and security, pilot licenses, etc. I thought this would be a good time to add a multivalue field to my tblEmployee table. I also decided to be adventurous, and use more than 1 column, even though I don't know if that actually works in this context and it isn't in my textbook. Now, I have 4 columns and 18 fields, and I'm wondering if this is a good idea? I'm especially wondering as the next window in the Lookup Wizard asks me which column I want to use that uniquely IDs the row, so it can store that value in my database. On one hand, a sub-table might make more sense. On the other, my grade depends on using as many Access tools as I can.
Any suggestions?