Search results

Once again you have pointed me in the right direction :) Please do post a calculation on how to handle punches that go over 24 hrs because I will have that situation. But I am going to create a separate table for payroll.

One more question, do i want to add this qry to an employee query or table in order to get data such as employee name pay and to calculate overtime for anything over 40 hours in a work period?

plog, you are correct my expected report is not actual calculations, they are just similar to what I want the data to show me for payroll purposes based on a period of one week. So time collected from Monday at say 5:30am until the following Monday at 5:29am would constitute a work week. Also...

Your first paragraph is spot on, I have a Work order for "Shop Time" which is for meetings, training, or anything else not attributed to a work order. I am not chaining the WOs together - they can clock-out of a work order and not clock back in on another one until later, that wouldn't matter...

So when they swipe their badge have a pop up for time sheet OR work order?

Please see the reply I just posted. Is that what you are guiding me to?

I must not understand what you are saying but I could add another form with Monday through Sunday for them to clock the payroll hours. Just seems redundant.

Your lunch comment has me thinking - right now when they clock-out on a work order my app displays a message box "Are you going home?" with a yes/no. If no, they clock in on another work order if yes it closes the time punch form and opens the dialog for anyone to scan an employee badge and...

Here is the Time Clock Data table and the way I envision the Payroll Data ( I did not calculate the times correctly on the payroll sheet because I didn't know how to do it in excel) I am open to any formatting that makes the calculations easier. The Time Worked column on the payroll sheet is...

No I do not pay them for lunch, but this is in conjunction with them clocking in on works orders and so I am trying to pick the first clock-in and the last clock-out for the day in order to get the payroll hours as well as the order tracking. The setup I have now is the one you don't like where...

I am modifying the test data. Will re upload the data sheet and will include an output sheet with it. Might take me a bit. thank you.

I guess the post posted itself while I was away from the keyboard. Here is the data file

A. Starting Data Table tblTimeClock Fields: TimeClockID - AutoNumber, WONumber - Short Text(not needed for this), TimeIn - Date/Time, TimeOut - Date/Time, EmpID - Number I have attached an excel file (tblTimeClockData) with the data and field names for A. above As far as B. goes the final...

I have a table that collects clock-in and clock-out "punches" for my employees to do Job tracking, the employee clock's in on a work order, then clocks out on that work order, then Clock's in on a new work order all through the day. so each entry in the timeclock table has two entries - an "in"...

Oh and yes a query is the record source, but not for the form. It works now though, not sure why but I can make the second scan and all is working. Very strange to me. Been struggling for many hours on it. I was starting to think that bouncing between too many front ends might be causing issues...

I have been having issues with my code running. Everything works great. I copy it to my home pc, re link the back end and then I have to open the code to get it to run. I don’t have to save it or anything, just put the form in design view, open the code window, go back to form view and it all...

Hmm, now that I think about it, I am creating the barcode by concatenating a number field and a text field in a query to get the query field for the barcode, like this, [Number] & "-" & [Text], but that is only to print the barcode.

Yes, No, and Yes

Yes, If I type something it fills in the field. But I did notice it doesn't go to the next field, just stays in the current field

I have a form that is unbound, I scan an employee badge and the after update event opens a Job tracking form that has a work order subform on it. when the job tracking form opens after some if/then statements, the form sets focus to a work order field and is waiting for input, when I scan the...