i must create a database for all the employees. it will contain normal fields such as name, address, SSN, phone, fax, mobile, job title, manager name, hire date, badge #, parking pass #, computer serial #, etc.<br><br>does anyone have any nice examples that will help me get started. i know Access has some sample databases if you go to 'Create a new database using a wizard' when starting Access, but it didn't have a Personnel example.<br><br>Thank you very much.<br>
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Anyone have any samples of a Personnel/Human Resources database?
- Thread starter ruthcali
- Start date
None of the databases the wizard provides are ideal. No matter how close it is, you still have to make changes. In this case, pick a database that will have some of the information you need for yours. You won't be able to delete any fields in the creation process, but after it's done, you can start making changes. Go through all the tables and make any necessary additions or deletions (remember, though, that changes in the tables will affect the forms and reports). Then go through all the forms and reports and adjust them to suit your requirements. Some you may delete, while others you may make major changes--or not at all.<br><br> <p>Linda Adams<br><a href=mailto:Garridon@aol.com>Garridon@aol.com</a><br><a href= Adams Online</a><br>I'm a professional writer, published internationally.
- Thread starter
- #3
hi,<br><br>Thanks for your response. i guess i am confused about relational databases. it seems to me like i could have all my info on one table:<br>employee name, address, phone, badge#, etc. <br><br>Why would i need more than one table? the only info that i can see repeating would be the Manager name. i guess i could put a manager code and then have another table with all the manager's names and their code numbers. this database will only hold about 40 records, so it isn't like i have to worry about size.<br><br>is there a disadvantage of putting all my data in just one table? that is why i wanted to look at an example of a database--to get an idea of the power of relational databases.<br><br>thank you very much,<br>ruth
You would be better off, reading about the advantages of Relational Databases. The documentation that comes with Access is a great place to start. <p>Jim Conrad<br><a href=mailto:jconrad3@visteon.com>jconrad3@visteon.com</a><br><a href= > </a><br>
Here's an example of why you should use more than one table.<br><br>You've just moved. You call your credit card company and give them your new address. Your bills come to your new address fine, but the extra stuff they send out goes to your old address. Why? Because this information exists in two different locations, and the second one wasn't updated. With a relational database, the new information is entered in once and is corrected everywhere.<br><br>It also takes up a lot less space to use a relational database. For instance, you have the state in your main table. Each time you enter information, you have to type California. That can take up a lot of space. But let's suppose now you create a table called States. You enter all the states once and relate the table to your main table. You use a combo box/drop down box (which your users appreciate) for the states on your form. The data is stored the number assigned to the state, so instead of California, it would be 2. And your user is happy because he doesn't have to type it out each time.<br><br> <p>Linda Adams<br><a href=mailto:Garridon@aol.com>Garridon@aol.com</a><br><a href= Adams Online</a><br>I'm a professional writer, published internationally.
- Thread starter
- #6
hi,<br><br>thanks for your input. but, if you were assigned to create a database for about 40 employees and it would contain 17 fields (name, address, phone, fax, cell, pager, email, badge, parking#, cube#, etc., how many tables would you create? i am so tempted to just make one table and put all the info in there. would that be considered sloppy programming?<br><br>Thanks,<br>ruth
I still would. As you develop it, you may find your boss wanting more fields, many more fields. It's better to start out with relational tables than having to go back and fix it.<br><br>Plus, it really does make a difference in size. My networking guy created a database with one table. It covered maybe 500 pieces of equipment if that and was three megs. I created one that covered over 2000 pieces of equipment and was around two megs--and I had reports, forms, and many more fields!<br> <p>Linda Adams<br><a href=mailto:Garridon@aol.com>Garridon@aol.com</a><br><a href= Adams Online</a><br>I'm a professional writer, published internationally.
"... contain 17 fields (name, address, phone, fax, cell, pager, email, badge, parking#, cube#, etc., how many tables would you create? "<br><br>I would create one(1) table for this information since it all relates to a single (atomic) entity; ie. 'employee'. Use an autonumber field for each of these records and you have your relational schema.<br><br>Later if you need to add records for say, attendance, insurance info, expense acct. history; you will then use the autonumber, the unique employee record key attached to each employee record, to link the new entries in the new tables to the single existing employee record.<br><br><br>Poof ! Relational database.<br><br> <p>Amiel<br><a href=mailto:amielzz@netscape.net>amielzz@netscape.net</a><br><a href= > </a><br>
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
