I've created an employee database but was asked to split off the security information into a separate table. The idea was to have other front ends that aren't connected to those specific tables to strengthen up confidential information. I'm pretty sure i went about this the wrong way and not sure how to get this setup correctly.... looking for some quick suggestions.
The attachment shows the 3 tables i'm dealing with now. I'm pretty sure I need a "SecurityID" in the employee table to reference the security table, but I have that being linked to the keyholder table already.
I had imported all the information into the security table which allowed it work, but with no link to the actual employee list, records will never be updated when new employees are added.
I have the 2 tables (security and keyholder) split up because the records in the security table are all unique to each employee, there will never be a duplicate. As for the keyholder table, an employee might have key access to multiple buildings, so I have that setup as a one to many relationship.
I'm hoping this is enough detail for someone to see what I have going on. I'm pretty sure its something simple and i'm just over-thinking it, could really use an outsiders opinion.
If more information is needed, let me know.
Thanks for the help!