Body
- Minor change to the queries that are first run after a long network disconnect - the BUZZER and M09 queries. The BUZZER query is first run after a CheckIn has started. M09 is first run when someone punches in, which may come after a long disconnect.
These queries were both updated with a different 'Error Message' so that if an error occurs, it is reported visually as a network error rather than a query error. These aren't complex queries, so it is unlikely that the query has failed but far more likely that the network has failed.
Normally this failure will recover eventually when the network access is restored, but the error is still presented on the screen for some reason as an 'Excessive Error' type of thing. Maybe this is an issue to take up in the next EurekaLog update.
The intent here is to give an error more indicative of the problem. Very few TimeClocks use the Buzzer system for example (currently ONE as of this writing I think) and ERR-M09 sounds more cryptic than it needs to be.
TimeClock v3.0.11.700 Statistics
Started: 2019-06-21 15:08:59
Finished: 2019-06-21 15:12:45
Elapsed: 00:03:46
File Size: 2,750,976
Source Lines: 488,934
UPX Time: 00:00:05
ZIP Time: 00:00:12
FTP Time: 00:03:29
ALL Time: 00:03:46