Logging inconsistencies

[Hafiz Bistar]

ELID DLL has different approach towards trans backup

[Clock Device ID: xx] [Date: DDMMYY] [Time: HHmm] [CardNo: xxxxxx] [JobCode: xxx] [Trans Code: y]

The OTA (which is self-written) is slightly different than that [ClockNo: xx] [Date: YYYYMMDD] [Time: HHmm] [CardNo: xxxxxx] [JobCode: xxx] [Trans Code: y]

x denotes any numbers, which replaced by 0 if the numbers are too small e.g 000006 for CardNo 6 y denotes the '<' and '>' symbol which means, IN or OUT transactions.

Only the first 2 parts are different. but will probably cause problem in the future.

[Patrick Ling]

I think we should make one standard format before any clock data is store in table.

[Hafiz Bistar]

(Reply via [e-mail]):

this is only the TransBackup logging data inconsistencies. Has no direct connection to Sync at the moment. But it will in the future

We cannot actually follow the elid's data format as the first data is already in consistence with the creation of Sync. Elid's approach limits the first data [clock device no] to 01-16. we change this part to make it so it can connect up to 64 clocks. hence 01-64.