Aloha - ADJTIME and ADJTIMEX 1

[blurngr]

We're writing some code which grabs Aloha time punch information and pulls it into our labor management application, and we're missing something with the ADJTIMEX grind files.

A customer changed a [fake] server's time punch on Oct 1, and then on Oct 14th, changed the Oct 1 time back. I was expecting to see an ADJTIMEX.DBF (or CSV) file in the Oct 14th grind directory. There isn't one.

How does Aloha handle this scenario? I understand that the time punches for today are in the ADJTIME.DBF file ... but where do the previous day's go? Any reason there wouldn't be an ADJTIMEX.DBF file?

Thanks!

--
Anthony

 

[alexander00pr]

I also had programed payroll interfaces. You should always grab the adjtime.dbf and gndbreak.dbf for time attendance purpose. The Adjtimex.dbf is synched with the adjtime.dbf when you manually grind that Date of business or when End of Day occur

For example:

1. Fake employee clock in/out at 6:00AM to 12:00PM on 20091023.

2. End of Day occurs.

3. Manager edit the Clock in/out to 6:30AM to 12:00PM on 20091025 at 10:00AM (In this case the adjtime.dbf will have the employee original punch and the adjtimex.dbf will have both the original punch and the edited punch. The difference is shown in the "invalid" colunmn in the dbf with a "Y or N". You will discard all punches with "Y" flag in the invalid column.). All of those changed will be in the 20091023 folder.

4. After EOD occurs the adjtimex.dbf will disappear and all punches will be synched to the adjtime.dbf file. If you manually run %iberdir%\BIN\grind.exe /date 20091023 this will cause the same effect on the adjtimex/adjtime files.

 

[blurngr]

Thanks! We just figured this out on Thursday afternoon ... but thanks very much!