H
HR 4 Life
I am having trouble getting started with an Access database to track keys
issued. Is anyone familiar and can help me get started?
issued. Is anyone familiar and can help me get started?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
T
tina
suggest the following, as
tblEmployees
EmpID (primary key. if employees already have a unique identifier in your
company, use that; otherwise, you can use an Autonumber. caution: suggest
you do NOT use SSN, Access is not secure enough for data that can be used
for identity theft.)
FirstName
LastName
<any other fields you need that describe an employee>
tblKeys
KeyID (primary key. again, if each key has a unique identifier, use that,
otherwise...)
<other fields that describe a key>
tblEmpKeys
EmpID (foreign key from tblEmployees)
KeyID (foreign key from tblKeys)
use the two fields as a combination primary key.
DateAssigned
DateReturned
<other fields that describe an instance of a specific key and a specific
employee.>
if one key unlocks multiple doors (like my work keys do), you may want a
table of locks (for room doors, building doors, whatever the keys unlock)
with a linking table to record what doors each key unlocks.
tblLocks
LockID (primary key, autonumber)
Location (what door the lock is attached to)
tblKeyLocks
KeyID (foreign key from tblKeys)
LockID (foreign key from tblLocks)
use the two fields as a combination primary key.
okay, the above is based on a lot of guesswork about your real-life
situation and what you actually need. my real-life recommendation is that
you learn the basics of relational design principles, and the basics of
building a relational database in Access; you're the best person to
determine how your database should be designed, once you know how - and even
the simplest database is worth doing right, because even the simplest
database can become a nightmare to work with if you build it wrong. for more
information on relational design and Access, see
http://home.att.net/~california.db/tips.html.
hth
tblEmployees
EmpID (primary key. if employees already have a unique identifier in your
company, use that; otherwise, you can use an Autonumber. caution: suggest
you do NOT use SSN, Access is not secure enough for data that can be used
for identity theft.)
FirstName
LastName
<any other fields you need that describe an employee>
tblKeys
KeyID (primary key. again, if each key has a unique identifier, use that,
otherwise...)
<other fields that describe a key>
tblEmpKeys
EmpID (foreign key from tblEmployees)
KeyID (foreign key from tblKeys)
use the two fields as a combination primary key.
DateAssigned
DateReturned
<other fields that describe an instance of a specific key and a specific
employee.>
if one key unlocks multiple doors (like my work keys do), you may want a
table of locks (for room doors, building doors, whatever the keys unlock)
with a linking table to record what doors each key unlocks.
tblLocks
LockID (primary key, autonumber)
Location (what door the lock is attached to)
tblKeyLocks
KeyID (foreign key from tblKeys)
LockID (foreign key from tblLocks)
use the two fields as a combination primary key.
okay, the above is based on a lot of guesswork about your real-life
situation and what you actually need. my real-life recommendation is that
you learn the basics of relational design principles, and the basics of
building a relational database in Access; you're the best person to
determine how your database should be designed, once you know how - and even
the simplest database is worth doing right, because even the simplest
database can become a nightmare to work with if you build it wrong. for more
information on relational design and Access, see
http://home.att.net/~california.db/tips.html.
hth
J
John... Visio MVP
Steve said:Tina's recommended tables are right on. If you need someone to put the
database together for you, I can do it for a very modest fee. If
interested, contact me at (e-mail address removed).
Steve
These newsgroups are provided by Microsoft for FREE peer to peer support.
Steve is a known troll and does not provide any services worth paying for.
He has repeatedly demonstrated his lack of talent by his posts to these
newsgroups.
John... VIsio MVP