If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Database Design question
I am designing a custom database for tracking various pieces of software we
use at my job. Each user has access to different pieces of software and many pieces of software require a separate username and password for each user. I'm trying to figure out the easiest/best way to do this. I'm using our and Employee table with EmployeeID as the PK and the EmployeeID FK in the Software table. I can either create a Software table that lists a field for each type of software and a separate username and password for each piece of software (which I know is poor database design) OR create a many to many relationship and create another table. The part that's throwing me off is the password/username part. Each person will have several usernames and passwords (one un/pw for each piece of software). Does anyone have any suggestions? I'm using Access 2007. |
Thread Tools | |
Display Modes | |
|
|