Timeclock bug

[cwathen]

Hi,

I seem to have found a bug with the timeclock. When using the option to view/print or amend a timecard, if you go back to a previous week, the program only displays the current week's dates.

The correct timecards with the correct timings and correct week end date are loaded, so the program is loading the correct files, it's just that it doesn't then calculate and display/print what the dates actually were for that week.

Chris

[dave something]

Just want to throw my "Yeah, me too" comment in on this topic.

Just printed two weeks of time cards and they all display this week's dates.

And, just because I'm picking nits...when you attempt to print time cards using the "print all cards with data" option, you actually get EVERY potential time card (meaning all 28 or so employee 'spaces' whether they're used or not, and NOT just those with data.

So, if I promise not to ask for additional features for the time clock, could you find it in your heart to stabilize the features already present?

Much appreciated.

[daleadmin]

Make a backup of your current TIMECLOK.EXE file and then download this http://www.dhpos.com/timeclok.exe and see if that fixes the date problem.

I just tried to print out all the time cards and only those with data printed. BTW, if a time card only has an employee name that counts as data.

You do know that nobody was actually supposed to use the time clock feature?

Dale

[dave something]

You do know that nobody was actually supposed to use the time clock feature?

I tried so hard to avoid it, but the employees kept punching in...

dave

[daleadmin]

dave something,

So does the fix work for you?

Dale

[daleadmin]

I tried so hard to avoid it, but the employees kept punching in...

Try removing the TIMECLOK.EXE program from the folder that holds the POS software. That will stop them.

Dale

[dave something]

Progress... but now new issues.

The dates are printing and recording fine, but now we have a couple new misfeatures that are a little more lethal:

1. Time stamps are not recording. When the user does the cntl-insert bit, the screen behavior shows the status change (green highlight to red highlight), but when they go to punch out later, there is no prior punch visible for the shift. If I go back and correct the punch, THAT data stays, but not the one generated by the user. If I simply use the View Timecards feature, no punch data will be visible for a user's shift if I have NOT corrected it already.

2. New .clk files are being created now that are not labeled with dates. In addition to the four regular time clock files, I now have four files labeled sequentially like 00000.clk, 00001.clk, 00002.clk, and 00003.clk. Selecting any of these files and attempting to open them will crash the entire POS system, not just the time clock program. They only started appearing AFTER I installed the last patch you provided.

Thanks in advance for whatever help you can provide.

**EDIT** As of this morning there is another wrinkle. When staff punch in today (Sunday, May 31) no new card file is created, so now I cannot go back and edit their time stamps (the need to do so explained above). In the meantime, I will go back to the previous timeclk.exe and at least have files corrected and time stamps remain. I can deal with the odd dates for the time being. Sorry to be a bother.

Dave

[cwathen]

I have the same issues with the new patch so have also reverted to the release version. There is a sort workaround in that if you change the system time to be in the week you want to print timecards for then you will get the correct dates for that week - but of course you need to be sure to change it back again when you're done.

[daleadmin]

OK, try this http://www.dhpos.com/timeclok.exe

On the screen when you enter the PIN number it will say "Version 7.02a" in the upper left corner.

Dale

[daleadmin]

So? Does the fix in 7.02a work?

Dale

[cwathen]

Unable to try yet as I've had a few days off - will let you know tomorrow when I get back in to work

[daleadmin]

Did anyone notice that when the program has a bug in it that people will tell me right away.

However when I post a fix folks have all the time in the world before they will tell me if it works?

So I guess that it must be working fine since if it had a bug they would have posted that long ago.

Dale

[AussieAussie]

Did anyone notice that when the program has a bug in it that people will tell me right away.

However when I post a fix folks have all the time in the world before they will tell me if it works?

So I guess that it must be working fine since if it had a bug they would have posted that long ago.

Dale

What's the old saying..........

No news is good news.

[cwathen]

Sorry for taking ages to get back to you! All seems to work perfectly in the new version, I think this can now be put into the standard download of the program.