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