Designing an attendence application

Hai Guys,

Iam working on a vb application to track attendence, overtime of employees.
We have implemented the system but has some issues which has to be solved.

we are capturing in and out time of employees using barcode.
when we scan the card for the first time in a day it will store the current time as signin time and next time it will be considered as signout and the time is captured.
Now when an employee is doing overtime say from 10 PM to 2 AM,
and he tries to signout at 2 AM the sytem will consider as signin since the date is changed.
In short the system is designed in such a way that every new entry in a day will be considered as signin.
How do i tackle this issue .

Thanks

Why not have every card swipe just toggle the status of the employee. One swipe in - one swipe out - next swipe in etc.. Why let the next day get in the way?

Quote:

---

Originally Posted by David.Poundall

Why not have every card swipe just toggle the status of the employee. One swipe in - one swipe out - next swipe in etc.. Why let the next day get in the way?

---

The problem is consider a situation the employee forgot to signout today.
tomorrow when he scan the card the system will consider it as signout.
to avoid this iam checking each entry with the date.

Thanks for your response.

Calculate the minimum amount of time off that is expected. If there hasn't been a time in/out that is longer than the minimum, then consider it signing out. If there has been that number of hours that have passed THEN consider it a sign in. You may have a 12 hour period, or you may have a 16 hour period, but that would eliminate someone being paid for 24 hours straight.

maybe make date effective from start of day shift, also if they don't sign out invite them not to come again

rgds pete

Quote:

---

The problem is consider a situation the employee forgot to signout today

---

well is it possible if the employee is sign in after 2 AM (let say 7 AM) and the prog check what is the last status for the employee..if the last status is sign in..then ur prog must set it to sign out (and set the sign out time to 7 AM since u can't record it)..so the employee can sign in again (at 7 AM)

but..dglienna seem have other option..

for the human error..u can't fix it with prog..it's the human's nature :D

the first time that they don't get paid because they forgot to sign out is usually the last time. we had a supervisor that actually was getting paid extra to keep track of sign-ins. she marched the guys into her office cubicle to sign in and out. 4x per day (lunches too).

of course, there has to be a way to over-ride the clock if necessary. just don't do it 'because they forgot'

if they are supposed to work from 12 to 8, and forget to sign out, the time between shifts is 0 and they have 24 hours of pay. the system would say they haven't been off for 12 hours, so negate the punch in that they did work, and create a new one for today.

they would have to get approval to be paid for the previous day. just like with a manual system, if you don't punch in, you don't get paid.

Quote:

---

Originally Posted by dew

The problem is consider a situation the employee forgot to signout today.
tomorrow when he scan the card the system will consider it as signout.
to avoid this iam checking each entry with the date.

---

You have to get involved manually to enter an out time from the day before anyway. Just record the swipe times and use them to do a best fit later - manually or automatically.

Clearly if there is longer than a shift + 20% between swipes a flag needs raising that the operator may not have swiped out. You may even be able to resolve the issue on the day because a quick check would reveal the missing worker - on the same day.

Don't sweat the front end as you need back end processing anyway.

.