HR sample access database

[Guest]

Hello,

Does anyone have a sample access database for a human resources department?
I'm a beginner and would like to see a sample of how a human resources
department database was created so that I can create one for myself.

Thanks!

 

[tina]

if you're planning on housing private and/or sensitive information in your
database, such as social security numbers, emergency contact information,
salaries, performance reviews/scores, etc, you need to keep in mind that an
Access database is not fully securable, even by skilled and experienced
developers, and consider the ramifications to your company if private data
were accessed by unauthorized personnel.

hth

 

[Guest]

Thanks for the heads up Tina. I just need sample database with sample data
in a University setting that I can use for training purposes. I asked for an
HR sample database, because everyone can relate to HR. If you know of an
easier way for me to create sample database that pertain to a University
setting, please let me know.

Thanks!

 

[tina]

hmm, well, there really is no "easy" way, only "right" and "wrong" ways.
right = a structure that meets your business needs while adhering to
standard rules of data normalization/relationships; wrong = a structure that
doesn't. just looking at somebody else's database won't help you much unless
you understand the principals behind the structure.

all i can recommend is that you read up on basic relational design
principals, then define your entities and data fields, model those into
appropriately related tables - and then post your results here if you want
to request 2nd opinions on the table/relationship structure.

see the webpage below for plenty of links to db design:

http://www.ltcomputerdesigns.com/JCReferences.html

hth

 

[Guest]

Thanks Tina!

hmm, well, there really is no "easy" way, only "right" and "wrong" ways.
right = a structure that meets your business needs while adhering to
standard rules of data normalization/relationships; wrong = a structure that
doesn't. just looking at somebody else's database won't help you much unless
you understand the principals behind the structure.

all i can recommend is that you read up on basic relational design
principals, then define your entities and data fields, model those into
appropriately related tables - and then post your results here if you want
to request 2nd opinions on the table/relationship structure.

see the webpage below for plenty of links to db design:

http://www.ltcomputerdesigns.com/JCReferences.html

hth