We're creating a database for our IS Dept that tracks PCUsers. The idea is, to give all Managers a Runtime that will allow them to request a User be added to our server, and also which Operating System (yep, we still have DOS users), software etc. Another area is Security. Our Accounting software requires permissions given by various owners within the software. We'd like the database to track requests, changes and approvals for security on that software, in addition to the requests previously stated.
So...I create the Users Table, a Software Table, but then I need to track severals yes/no options for permissions within the Accounting software. 8 different areas have 15 different yes/no questions. We want the Manager to have the ability to view the user's status at the various stages of approval.
That's where I'm stuck. The user can have permissions in more than one area of the Accounting Software. Each of the 8 areas 15 questions are unique.
I'd like to read your take on how you'd design this database. Every option I've come up with, ends up duplicating information.
Thanks in advance,
Rhonda
So...I create the Users Table, a Software Table, but then I need to track severals yes/no options for permissions within the Accounting software. 8 different areas have 15 different yes/no questions. We want the Manager to have the ability to view the user's status at the various stages of approval.
That's where I'm stuck. The user can have permissions in more than one area of the Accounting Software. Each of the 8 areas 15 questions are unique.
I'd like to read your take on how you'd design this database. Every option I've come up with, ends up duplicating information.
Thanks in advance,
Rhonda