I think my problem might not that the field that I thought it should be actually is wrong and I won't need the calculated field if the fix goes through correctly. But the field that I am (was) looking for is on the time and expense screen. Tabs "time" "daily time" "Summary" "detail". The field is on the bottom row, total labor.
But like I said, I don't think that this is the actual field that I want. I'm looking for pay hours, and I think my system isn't taking out the lunches correctly so the pay hours is showing 30 min (or an hour depending on the shift chosen) too high because it's not taking out lunch automatically. The total labor is taking out that time, so I was thinking that the total labor was the pay hours with the lunch taken out, but through the process I'm realizing that total labor is actually the total time when someone is clocked into a job, or indirect labor, not actual clock in-out pay time. They are just basically the same in enough cases that I was tricked into thinking they were the same.
Once our test system comes back up I'll try to confirm this (we had lots of crashes yesterday on day 2 of our go live). On another thread, someone showed me that there is supposed to be a fix for this problem.
Thanks for your help.
Brandon
But like I said, I don't think that this is the actual field that I want. I'm looking for pay hours, and I think my system isn't taking out the lunches correctly so the pay hours is showing 30 min (or an hour depending on the shift chosen) too high because it's not taking out lunch automatically. The total labor is taking out that time, so I was thinking that the total labor was the pay hours with the lunch taken out, but through the process I'm realizing that total labor is actually the total time when someone is clocked into a job, or indirect labor, not actual clock in-out pay time. They are just basically the same in enough cases that I was tricked into thinking they were the same.
Once our test system comes back up I'll try to confirm this (we had lots of crashes yesterday on day 2 of our go live). On another thread, someone showed me that there is supposed to be a fix for this problem.
Thanks for your help.
Brandon