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
|
|||
|
|||
Overtime DB Help Needed
I'm trying to design a DB that will keep track of overtime hours and date. I
have a table of employees, table of equipment they work on and table of date and hours for overtime worked. I want to sort by equipment each employee can work on, then total overtime hours and then seniority. I would like this displayed on a form and then be able to assign hours and date worked. I tried this using a query and form but I can't update the query after it's run. Please help and thanks in advance! |
#2
|
|||
|
|||
Overtime DB Help Needed
To get an answer or suggestions appropriate to your situation you'll
need to supply a lot more details about your real-world situation and the desired workflow. You don't need all of the information in your query in order to assign new overtime work on something they're qualified to do. To that end you could make the action of selecting the person most eligible for overtime in the current situation open a new form for purpose of assigning/authorizing. My gut feeling is that the only form required would be the one to assign/authorize the overtime by a particular employee. In the header of that form would be two comboboxes. The first combobox would be based on a lookup table that has all of the equipment. When the equipment is selected it should be entered in the correct control on the form. The second combobox would be based on a query similar to the one you now have.. Simply selecting the most eligible employee in the second combobox would then (in its AfterUpdate event) put the appropriate information from the second combobox into appropriate controls on the form. The flaw in the simplistic algorithm suggested above is that the real-world is rarely that simple. It assumes that the most eligible employee is always ready, willing and able to do the thing in question. There is no provision for unavailability for any reason whatever. In the real-world you might have to work your way down a list of eligible employees until the required number of them sigh on. HTH -- -Larry- -- "Bill" wrote in message ... I'm trying to design a DB that will keep track of overtime hours and date. I have a table of employees, table of equipment they work on and table of date and hours for overtime worked. I want to sort by equipment each employee can work on, then total overtime hours and then seniority. I would like this displayed on a form and then be able to assign hours and date worked. I tried this using a query and form but I can't update the query after it's run. Please help and thanks in advance! |
#3
|
|||
|
|||
Overtime DB Help Needed
Thank you Larry for the reply this is driving me nuts, seems so hard to
accomplish. Overtime is assigned on the basis of need. Not all employees know how to work on every piece of equipment. When there is a need for OT the employee with the least amount of OT and has knowledge of the piece of equipment is asked to work. The tie breaker is seniority. If the employee doesn’t want to work they are charged for decline that adds to total hours. There are different types of equipment such as computer bds, power supplies, memory bds, barcode readers, etc. So I would like to have all employees in a database, based on my need example computer bd A sort through a list of employees that can perform the job, give me a list of employees with least hours first with tie breaker going to seniority. That’s the easy part. The hard part is a want to be able to update the database when I assign the hours using a form by hours and date worked. Example: Computer bd A Employee A. Seniority 7 Hours 10 Enter Hours: Enter Date: Employee B Seniority 5 Hours 14 Enter Hours: Enter Date: Employee C Seniority 3 Hours 20 Enter Hours: Enter Date: Employee D Seniority 6 Hours 25 Enter Hours: Enter Date: Thanks again in advance! "Larry Daugherty" wrote: To get an answer or suggestions appropriate to your situation you'll need to supply a lot more details about your real-world situation and the desired workflow. You don't need all of the information in your query in order to assign new overtime work on something they're qualified to do. To that end you could make the action of selecting the person most eligible for overtime in the current situation open a new form for purpose of assigning/authorizing. My gut feeling is that the only form required would be the one to assign/authorize the overtime by a particular employee. In the header of that form would be two comboboxes. The first combobox would be based on a lookup table that has all of the equipment. When the equipment is selected it should be entered in the correct control on the form. The second combobox would be based on a query similar to the one you now have.. Simply selecting the most eligible employee in the second combobox would then (in its AfterUpdate event) put the appropriate information from the second combobox into appropriate controls on the form. The flaw in the simplistic algorithm suggested above is that the real-world is rarely that simple. It assumes that the most eligible employee is always ready, willing and able to do the thing in question. There is no provision for unavailability for any reason whatever. In the real-world you might have to work your way down a list of eligible employees until the required number of them sigh on. HTH -- -Larry- -- "Bill" wrote in message ... I'm trying to design a DB that will keep track of overtime hours and date. I have a table of employees, table of equipment they work on and table of date and hours for overtime worked. I want to sort by equipment each employee can work on, then total overtime hours and then seniority. I would like this displayed on a form and then be able to assign hours and date worked. I tried this using a query and form but I can't update the query after it's run. Please help and thanks in advance! |
#4
|
|||
|
|||
Overtime DB Help Needed
You didn't mention my suggestions so you obviously must understand why
and how to implement them. You're still keeping secrets. You want to use your Access application to control a process and arrive at a correct result. You haven't defined the details of the workflow required to get from the ordered list of qualified individuals to selecting the correct number of qualified individuals to fulfill the requirements. You must fully define the workflow through its completion. Your last response just got us to a point where you're ready to take an action (offering an individual the work) and taking subsequent action based on the results of that first action. Conceptually we had been at that point before. You need to be thinking in terms of what you're trying to accomplish in the real-world and then apply the 'journalistic catechism" at each step: Who, What, When, Where, Why, How and, Larry's addition, What next? My answers are done until you add the missing details of undefined levels or ask new questions. In either of those cases, please post back. HTH -- -Larry- -- "Bill" wrote in message ... Thank you Larry for the reply this is driving me nuts, seems so hard to accomplish. Overtime is assigned on the basis of need. Not all employees know how to work on every piece of equipment. When there is a need for OT the employee with the least amount of OT and has knowledge of the piece of equipment is asked to work. The tie breaker is seniority. If the employee doesn't want to work they are charged for decline that adds to total hours. There are different types of equipment such as computer bds, power supplies, memory bds, barcode readers, etc. So I would like to have all employees in a database, based on my need example computer bd A sort through a list of employees that can perform the job, give me a list of employees with least hours first with tie breaker going to seniority. That's the easy part. The hard part is a want to be able to update the database when I assign the hours using a form by hours and date worked. Example: Computer bd A Employee A. Seniority 7 Hours 10 Enter Hours: Enter Date: Employee B Seniority 5 Hours 14 Enter Hours: Enter Date: Employee C Seniority 3 Hours 20 Enter Hours: Enter Date: Employee D Seniority 6 Hours 25 Enter Hours: Enter Date: Thanks again in advance! "Larry Daugherty" wrote: To get an answer or suggestions appropriate to your situation you'll need to supply a lot more details about your real-world situation and the desired workflow. You don't need all of the information in your query in order to assign new overtime work on something they're qualified to do. To that end you could make the action of selecting the person most eligible for overtime in the current situation open a new form for purpose of assigning/authorizing. My gut feeling is that the only form required would be the one to assign/authorize the overtime by a particular employee. In the header of that form would be two comboboxes. The first combobox would be based on a lookup table that has all of the equipment. When the equipment is selected it should be entered in the correct control on the form. The second combobox would be based on a query similar to the one you now have.. Simply selecting the most eligible employee in the second combobox would then (in its AfterUpdate event) put the appropriate information from the second combobox into appropriate controls on the form. The flaw in the simplistic algorithm suggested above is that the real-world is rarely that simple. It assumes that the most eligible employee is always ready, willing and able to do the thing in question. There is no provision for unavailability for any reason whatever. In the real-world you might have to work your way down a list of eligible employees until the required number of them sigh on. HTH -- -Larry- -- "Bill" wrote in message ... I'm trying to design a DB that will keep track of overtime hours and date. I have a table of employees, table of equipment they work on and table of date and hours for overtime worked. I want to sort by equipment each employee can work on, then total overtime hours and then seniority. I would like this displayed on a form and then be able to assign hours and date worked. I tried this using a query and form but I can't update the query after it's run. Please help and thanks in advance! |
#5
|
|||
|
|||
Overtime DB Help Needed
|
#6
|
|||
|
|||
Overtime DB Help Needed - Stevie just does not get it!
"Steve" wrote in message
... Hi Bill, Give me a chance to relieve your frustration; I can help you. I provide help with Access applications for a very modest fee. Contact me if you would like my help. Steve Stevie, you are hopeless. These newsgroups are provided by Microsoft for FREE peer to peer support. There are many highly qualified individuals who gladly help for free. Stevie is not one of them, but he is the only one who just does not get the idea of "FREE" support. He offers questionable results at unreasonable prices. If he was any good, the "thousands" of people he claims to have helped would be flooding him with work, but there appears to be a continuous drought and he needs to constantly grovel for work. A few gems gleaned from the Word New User newsgroup over the Christmas holidays to show Stevie's "expertise" in Word. Dec 17, 2008 7:47 pm Word 2007 .......... In older versions of Word you could highlght some text then go to Format - Change Case and change the case of the hoghloghted text. Is this still available in Word 2007? Where? Thanks! Steve Dec 22, 2008 8:22 pm I am designing a series of paystubs for a client. I start in landscape and draw a table then add columns and rows to setup labels and their corresponding value. This all works fine. After a landscape version is completed, I next need to design a portrait version. Rather than strating from scratch, I'd like to be able to cut and paste from the landscape version and design the portrait version. Steve Dec 24, 2008, 1:12 PM How do you protect the document for filling in forms? Steve One of my favourites: Dec 30, 2008 8:07 PM - a reply to stevie (The original poster asked how to sort a list and stevie offered to create the OP an Access database) Steve wrote: Yes, you are right but a database is the correct tool to use not a spreadsheet. Not at all. If it's just a simple list then a spreadsheet is perfectly adequate... John... Visio MVP |
#7
|
|||
|
|||
Overtime DB Help Needed
On Tue, 4 Aug 2009 11:56:39 -0400, "Steve" wrote:
Hi Bill, Give me a chance to relieve your frustration; I can help you. I provide help with Access applications for a very modest fee. Contact me if you would like my help. http://www.microsoft.com/library/gal...RulesofConduct Rules of conduct Appropriate Language: The purpose of our communities is to exchange technical information and expertise about Microsoft products. Please avoid personal attacks, slurs, and profanity in your interactions. Relevance to Topics: Please make sure that your postings in discussion groups and chats are relevant to the subject at hand. It is normal for some topics to drift from the stated subject. However, to ensure maximum benefit for everyone, we encourage you to keep your postings as close to the subject as possible. Advertising/Solicitation: These communities were created as a forum for providing peer-to-peer assistance on Microsoft products and services. **We ask that you refrain from posting advertisements or solicitations that do not pertain directly to the intended use and purpose of the newsgroup or chat.** -- John W. Vinson [MVP] |
#8
|
|||
|
|||
Overtime DB Help Needed
|
#9
|
|||
|
|||
Overtime DB Help Needed
It may help if you can gain more understanding of the language of relational
databases. Ths link may help: http://allenbrowne.com/casu-22.html The Index of Tips at the bottom of the web page includes more help. That page includes a Links link to yet more resources. "Bill" wrote in message ... Thank you Larry for the reply this is driving me nuts, seems so hard to accomplish. Overtime is assigned on the basis of need. Not all employees know how to work on every piece of equipment. When there is a need for OT the employee with the least amount of OT and has knowledge of the piece of equipment is asked to work. The tie breaker is seniority. If the employee doesn't want to work they are charged for decline that adds to total hours. There are different types of equipment such as computer bds, power supplies, memory bds, barcode readers, etc. So I would like to have all employees in a database, based on my need example computer bd A sort through a list of employees that can perform the job, give me a list of employees with least hours first with tie breaker going to seniority. That's the easy part. The hard part is a want to be able to update the database when I assign the hours using a form by hours and date worked. Example: Computer bd A Employee A. Seniority 7 Hours 10 Enter Hours: Enter Date: Employee B Seniority 5 Hours 14 Enter Hours: Enter Date: Employee C Seniority 3 Hours 20 Enter Hours: Enter Date: Employee D Seniority 6 Hours 25 Enter Hours: Enter Date: Thanks again in advance! "Larry Daugherty" wrote: To get an answer or suggestions appropriate to your situation you'll need to supply a lot more details about your real-world situation and the desired workflow. You don't need all of the information in your query in order to assign new overtime work on something they're qualified to do. To that end you could make the action of selecting the person most eligible for overtime in the current situation open a new form for purpose of assigning/authorizing. My gut feeling is that the only form required would be the one to assign/authorize the overtime by a particular employee. In the header of that form would be two comboboxes. The first combobox would be based on a lookup table that has all of the equipment. When the equipment is selected it should be entered in the correct control on the form. The second combobox would be based on a query similar to the one you now have.. Simply selecting the most eligible employee in the second combobox would then (in its AfterUpdate event) put the appropriate information from the second combobox into appropriate controls on the form. The flaw in the simplistic algorithm suggested above is that the real-world is rarely that simple. It assumes that the most eligible employee is always ready, willing and able to do the thing in question. There is no provision for unavailability for any reason whatever. In the real-world you might have to work your way down a list of eligible employees until the required number of them sigh on. HTH -- -Larry- -- "Bill" wrote in message ... I'm trying to design a DB that will keep track of overtime hours and date. I have a table of employees, table of equipment they work on and table of date and hours for overtime worked. I want to sort by equipment each employee can work on, then total overtime hours and then seniority. I would like this displayed on a form and then be able to assign hours and date worked. I tried this using a query and form but I can't update the query after it's run. Please help and thanks in advance! |
#10
|
|||
|
|||
Overtime DB Help Needed
Rules of conduct
Appropriate Language: ..... Please avoid personal attacks, slurs, and profanity in your interactions. Why don't you point this out to Visio John, Gina Whipp, Keith Wilby, Bruce M and Bob Quintal? Of course some are MVPs like you and you wouldn't go against another MVP. "John W. Vinson" wrote in message ... On Tue, 4 Aug 2009 11:56:39 -0400, "Steve" wrote: Hi Bill, Give me a chance to relieve your frustration; I can help you. I provide help with Access applications for a very modest fee. Contact me if you would like my help. http://www.microsoft.com/library/gal...RulesofConduct Rules of conduct Appropriate Language: The purpose of our communities is to exchange technical information and expertise about Microsoft products. Please avoid personal attacks, slurs, and profanity in your interactions. Relevance to Topics: Please make sure that your postings in discussion groups and chats are relevant to the subject at hand. It is normal for some topics to drift from the stated subject. However, to ensure maximum benefit for everyone, we encourage you to keep your postings as close to the subject as possible. Advertising/Solicitation: These communities were created as a forum for providing peer-to-peer assistance on Microsoft products and services. **We ask that you refrain from posting advertisements or solicitations that do not pertain directly to the intended use and purpose of the newsgroup or chat.** -- John W. Vinson [MVP] |
|
Thread Tools | |
Display Modes | |
|
|