A Microsoft Office (Excel, Word) forum. OfficeFrustration

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.

Go Back   Home » OfficeFrustration forum » Microsoft Access » New Users
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

building employee db



 
 
Thread Tools Display Modes
  #1  
Old October 26th, 2007, 02:30 AM posted to microsoft.public.access.gettingstarted
mdooley
external usenet poster
 
Posts: 1
Default building employee db

I am currently trying to build an employee db of 150+ employees where, for
the most part, all HR information will be kept. Information as simple as
name, address, phone to retirement info, insurance premium changes and
tracking salary increases, etc. My first dilemma - to build one or more
tables. If I build only one table it will be very large. If I build more
than one it seems to me that there would be only one to one relationships?
The second dilemma - how I go about tracking for example pay increases. And
in the form (which I hope to be able to input all the info) how can I add the
new pay amount (in case of a raise) without overriding the previous pay
amount - so that I can track it over time. Any help is appreciated...I am
relatively new at this.

  #2  
Old October 26th, 2007, 05:00 AM posted to microsoft.public.access.gettingstarted
Beetle
external usenet poster
 
Posts: 1,254
Default building employee db

You will DEFINETLY need more than one table, and it is highly unlikely that
you would have only one-to-one relationships. Take your pay increases for
example. You would have one table that holds information about the employee
(LastName, FirstName, Address, etc.) and another table that holds information
about an employees salary (which would probably include a Date field so you
could track when a pay raise was given). Since one employee can have many pay
raises, then this would constitute a one-to-many relationship. I can't tell
you exactly how to set up your tables since I don't really know anything
about or DB, but I recommend you do some research on proper table design
before you get started. Here are some links that you may find helpful.

http://www.accessmvp.com/JConrad/acc...resources.html

http://allenbrowne.com/casu-22.html

http://www.databasedev.co.uk/tables.html

HTH


--
_________

Sean Bailey


"mdooley" wrote:

I am currently trying to build an employee db of 150+ employees where, for
the most part, all HR information will be kept. Information as simple as
name, address, phone to retirement info, insurance premium changes and
tracking salary increases, etc. My first dilemma - to build one or more
tables. If I build only one table it will be very large. If I build more
than one it seems to me that there would be only one to one relationships?
The second dilemma - how I go about tracking for example pay increases. And
in the form (which I hope to be able to input all the info) how can I add the
new pay amount (in case of a raise) without overriding the previous pay
amount - so that I can track it over time. Any help is appreciated...I am
relatively new at this.


  #3  
Old October 26th, 2007, 03:21 PM posted to microsoft.public.access.gettingstarted
mdooley via AccessMonster.com
external usenet poster
 
Posts: 9
Default building employee db

Thanks for the help and the links - I will take a look at them and keep
working at my db. I am SURE I will have more questions.

Beetle wrote:
You will DEFINETLY need more than one table, and it is highly unlikely that
you would have only one-to-one relationships. Take your pay increases for
example. You would have one table that holds information about the employee
(LastName, FirstName, Address, etc.) and another table that holds information
about an employees salary (which would probably include a Date field so you
could track when a pay raise was given). Since one employee can have many pay
raises, then this would constitute a one-to-many relationship. I can't tell
you exactly how to set up your tables since I don't really know anything
about or DB, but I recommend you do some research on proper table design
before you get started. Here are some links that you may find helpful.

http://www.accessmvp.com/JConrad/acc...resources.html

http://allenbrowne.com/casu-22.html

http://www.databasedev.co.uk/tables.html

HTH

I am currently trying to build an employee db of 150+ employees where, for
the most part, all HR information will be kept. Information as simple as

[quoted text clipped - 7 lines]
amount - so that I can track it over time. Any help is appreciated...I am
relatively new at this.


--
Message posted via http://www.accessmonster.com

  #4  
Old October 26th, 2007, 03:39 PM posted to microsoft.public.access.gettingstarted
gls858
external usenet poster
 
Posts: 473
Default building employee db

mdooley wrote:
I am currently trying to build an employee db of 150+ employees where, for
the most part, all HR information will be kept. Information as simple as
name, address, phone to retirement info, insurance premium changes and
tracking salary increases, etc. My first dilemma - to build one or more
tables. If I build only one table it will be very large. If I build more
than one it seems to me that there would be only one to one relationships?
The second dilemma - how I go about tracking for example pay increases. And
in the form (which I hope to be able to input all the info) how can I add the
new pay amount (in case of a raise) without overriding the previous pay
amount - so that I can track it over time. Any help is appreciated...I am
relatively new at this.


While this can be done in Access sometimes it's much more economical to
buy an off the shelf program designed specifically for your needs. If
you're just wanting to learn Access this could be a very in depth
project. OTH if you're need this right away I would look for a software
package designed for HR. One that I looked at was Softime the link is
below. It's not real expensive. You might want to take a look.

Standard disclaimer: I don't work for or am I associated with yada yada

http://www.softwaretech.com/


gls858
  #5  
Old October 26th, 2007, 11:33 PM posted to microsoft.public.access.gettingstarted
mscertified
external usenet poster
 
Posts: 835
Default building employee db

In my opinion, Access is not a secure enough database to hold this kind of
sensitive information. And if such private information should become
compromised, you could be open to a large lawsuit. Think carefully before you
store information like SSN or any data that can be used for identity theft in
such an unsecure database.

"mdooley" wrote:

I am currently trying to build an employee db of 150+ employees where, for
the most part, all HR information will be kept. Information as simple as
name, address, phone to retirement info, insurance premium changes and
tracking salary increases, etc. My first dilemma - to build one or more
tables. If I build only one table it will be very large. If I build more
than one it seems to me that there would be only one to one relationships?
The second dilemma - how I go about tracking for example pay increases. And
in the form (which I hope to be able to input all the info) how can I add the
new pay amount (in case of a raise) without overriding the previous pay
amount - so that I can track it over time. Any help is appreciated...I am
relatively new at this.


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 04:41 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.