If this is a Perl question, my eyes must be going .. I can't see any, apart from a mention of CPAN (and what key words did you say you used for your CPAN search?)
From a database schema point of view (something I love to kick around), I'd probably create an event table with some sort of Employee ID, a timestamp and an event type (in, out, going to lunch, back from lunch). I'd have another table that holds the current status of an employee, so that if an employee tries to go to lunch when they forgot to punch in, the application would raise an alarm. Hmm .. actually, forget the second table, we can just go back and look at the most recent entry for that employee and see if the new entry makes sense. Yeah. Less is More.
Then there are the safety catches like flagging when an employee has stayed past 6pm (say) but hasn't clocked out yet.
Interesting question. But still not Perl.
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
In reply to Re: PERL/MySQL Punch Clock
by talexb
in thread PERL/MySQL Punch Clock
by amt
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |