View Single Post
  #2  
Old November 5th, 2008, 09:50 PM posted to microsoft.public.access.tablesdbdesign
Beetle
external usenet poster
 
Posts: 1,254
Default Database Design question

As far as keeping track of the various user names an passwords, you
could add a third (junction) table that woul handle this. For example;

tblEmployees
**********
EmployeeID (Primary Key)
FirstName
LastName
other attributes of the Employee

tblSoftware
********
SoftwareID (PK)
Description
other attributes of the software

tblPasswords (the junction table)
**********
EmployeeID (Foreign Key to tblEmployees)
SoftwareID (FK to tblSoftware)
UserName
Password

EmployeeID and SoftwareID woul be a composite PK in the junction
table. Each record in this table would hold the valid user name and
password for any given combination of Employee/Software Item
--
_________

Sean Bailey


"Carrie" wrote:

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.