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. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
table / query design
Hello,
I would like to ask advice on database / query design. I intend to create a salary calculator in Access 2007. In my plan there are different job positions and different salary categories for each job positions. For example job positions: boss assistant worker And there are salary categories: Normal Saturday Sunday 48hours Then I could combine different job positions with different salary categories. My tables a tbl_jobpositions jobpositionsID basicsalary tbl_salarycategories salarycategoriesID salarycategory tbl_salaries salariesID jobpositionsID salarycategoriesID I created a query that calculates all the salary possibilities for each job position. The first field is coming from a table field the rest are calculated fields. Jobpositions Normal Saturday Sunday ………….. Boss calculated calculated calculated Assistant calculated calculated calculated Worker calculated calculated calculated And at this point I am stuck. I don’t know how to retrieve the calculated data from the query, how to look up a data from the query according to the tbl_salaries table. I can use criteria to show records in the query but I don’t know how select fields in the query. Or maybe I am going in a wrong direction? Any one can give me advice? Thanks in advance ffulmer -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/201003/1 |
#2
|
|||
|
|||
table / query design
I noticed that nobody answered.
On your later question, I think that you are making the mistake of mostly skipping over step 1 and step 2: Step 1 Clearly decribe the database-relevant aspects of the real world process that you want to database, and the mission that you want your database to accomplish. Especially decide what the entities are that you want to database, and what the relationships are between them. Decide what types of “one to one” information/attributes you want to store/record for each entity. If you run across a “many to one” situation, (like many phone numbers for each company) consider that to be an entity. Do all of this without using any Access terminology. If you need structural help (as I think you do) describe what you came up with under step 1 in your post. Step 2 Design a good table structure which will accomplish databasing your process and support accomplishment of your mission. Generally, each entity will get a table, and each one-to-one type piece of information about that entity will get a field in that table. Step 3 Design queries, forms, reports etc. to accomplish your mission. Hope that helps a little. |
#3
|
|||
|
|||
table / query design
Hi Fred,
Thank you for your comment. ffulmer -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/201003/1 |
Thread Tools | |
Display Modes | |
|
|