By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,871 Members | 2,304 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,871 IT Pros & Developers. It's quick & easy.

Clocking out database help

P: n/a
i currently have a database for tracking members arrival and exit
times. however due to new demands my training centre are wanting a
barcode system setup where all the user has to do is use a wedge
scanner and not need to touch the mouse or keyboard. i can
successfully clock in but i am havin difficulties when it comes to
clocking out i am no good with VBA code but if anyone could help me
with if true statements or other ways to produce this outcome. much
appreciated.

Feb 12 '07 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Hi There,

I am going to assume (perhaps dangerously) that if you can "clock in"
people to the site, then you can successfully read the data that is
coming from the scanner. The way that "clock in / clock out" stuff is
typically handled in security or time and attendance type applications
is to have a log of the activities with maybe a username / number and
the time of the event, and the in or out status.

The way the in / out status is handled is to run a separate table that
holds the users unique ID in it. When the user "clocks in" their ID is
added to this second table as well as the event being added to the
log, then when the user ID is entered again (in this case by the
scanner reading the barcode) the in/out table is checked to see if the
user ID is already there, if it is then the user must be "clocking
out", and if it isnt then the user must be "clocking in". If the user
is clocking out then I would suggest simply deleting the ID from the
in/out table and making an entry in the log (if you need to log these
things).

It would be easiest to do this with a little VBA and a simple IF
statement. Psuedo code below:

DataVar = scanner data read
if DataVar in TableClockInOut then
delete DataVar from TableClockInOut
else
add DataVar into TableClockInOut
end if

This is of course not real code, but the logic is probably what you
need. If you can post what you are using to generate the "clock in"
other readers or I may be able to help you write what is needed to
finish the job properly.

I hope that this helps

Cheers

The Frog

Feb 12 '07 #2

P: n/a
And of course now you have to work out procedurally what you are going
to do about a missed punch.

If the persons forgets to clock out, then you interpret his next days
in as a Out

Then again if they forget the in punch then you consider their out
punch as the in punch.

Just thought I would add some wrenches to your thinking process.

Try to avoid doing what our clock system sometimes does: It will take
my 4 daily punches (in, then out for lunch, then in from lunch, then
leaving work) and simply jumbles them around randomly. I think someone
does it to force my manager to think in circles.

Good Luck.

Ron

Feb 12 '07 #3

P: n/a

"Ron2006" <ro******@hotmail.comwrote in message
news:11**********************@m58g2000cwm.googlegr oups.com...
And of course now you have to work out procedurally what you are going
to do about a missed punch.

If the persons forgets to clock out, then you interpret his next days
in as a Out

Then again if they forget the in punch then you consider their out
punch as the in punch.

Just thought I would add some wrenches to your thinking process.

Try to avoid doing what our clock system sometimes does: It will take
my 4 daily punches (in, then out for lunch, then in from lunch, then
leaving work) and simply jumbles them around randomly. I think someone
does it to force my manager to think in circles.

Good Luck.

Ron
Limit the time allowed between clock-in and clock-out to say 18 hours.
Employee clock-in at 6:00 AM and the next clock punch is at 5:59 AM on the
next day, assume this is also a clock-in with no clock-out for the previous
day.
Feb 13 '07 #4

P: n/a
On Feb 13, 8:13 am, "paii, Ron" <p...@packairinc.comwrote:
"Ron2006" <ronne...@hotmail.comwrote in message

news:11**********************@m58g2000cwm.googlegr oups.com...


And of course now you have to work out procedurally what you are going
to do about a missed punch.
If the persons forgets to clock out, then you interpret his next days
in as a Out
Then again if they forget the in punch then you consider their out
punch as the in punch.
Just thought I would add some wrenches to your thinking process.
Try to avoid doing what our clock system sometimes does: It will take
my 4 daily punches (in, then out for lunch, then in from lunch, then
leaving work) and simply jumbles them around randomly. I think someone
does it to force my manager to think in circles.
Good Luck.
Ron

Limit the time allowed between clock-in and clock-out to say 18 hours.
Employee clock-in at 6:00 AM and the next clock punch is at 5:59 AM on the
next day, assume this is also a clock-in with no clock-out for the previous
day.- Hide quoted text -

- Show quoted text -

madgunnercurz,
The reply is one way, Just don't forget to address the problem,
because it WILL happen. (Maybe it is a power outage at the end of the
day, so NO ONE can log out. - hmmmm)

Ron

Feb 13 '07 #5

P: n/a
How you handle missing clock-out is up to you, I create a clock-out with the
same date and time as the clock-in.

"Ron2006" <ro******@hotmail.comwrote in message
news:11**********************@m58g2000cwm.googlegr oups.com...
On Feb 13, 8:13 am, "paii, Ron" <p...@packairinc.comwrote:
"Ron2006" <ronne...@hotmail.comwrote in message

news:11**********************@m58g2000cwm.googlegr oups.com...


And of course now you have to work out procedurally what you are going
to do about a missed punch.
If the persons forgets to clock out, then you interpret his next days
in as a Out
Then again if they forget the in punch then you consider their out
punch as the in punch.
Just thought I would add some wrenches to your thinking process.
Try to avoid doing what our clock system sometimes does: It will take
my 4 daily punches (in, then out for lunch, then in from lunch, then
leaving work) and simply jumbles them around randomly. I think someone
does it to force my manager to think in circles.
Good Luck.
Ron
Limit the time allowed between clock-in and clock-out to say 18 hours.
Employee clock-in at 6:00 AM and the next clock punch is at 5:59 AM on
the
next day, assume this is also a clock-in with no clock-out for the
previous
day.- Hide quoted text -

- Show quoted text -


madgunnercurz,
The reply is one way, Just don't forget to address the problem,
because it WILL happen. (Maybe it is a power outage at the end of the
day, so NO ONE can log out. - hmmmm)

Ron

Feb 13 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.