Version 2.2.11 Released

A small release today fixing up a couple of issues and adding some formatting to a couple of reports.

  • Employees on a fortnightly salary period had their hours calculated incorrectly. This is now fixed up.
  • If you unchecked all of the employees on the report configuration screen and then tried to run a report by department or shift an incorrect warning was displayed and you could not run the report. This is now fixed.
  • The minimize button on the report display screen has been de-activated. If you clicked on this it caused a hard crash.
  • The punchard and detailed punch card reports now have blocks of data separated by weeks. This is just to make for easier reading of the report.

Version 2.3.2 Released

A new minor release of Time Clock MTS today fixing up a few problems. Details of the fixes are below:

  • Some fixes to the way resizing of the application window works. In some cases the bottom employee on the employee list wouldn’t be visible, I think this is because of the scroll bars appearing on the list of employees. This should be fixed up now, along with the maximize window button being disabled when you’re using the keypad interface.
  • A fix to the mySQL database creation script, for some reason LONGTEXT fields were being set to VARCHAR(255). Now all fixed.
  • Fix to all payroll reports where the monthly pay amount was more than $9,999.99. Wages now display and print correctly.
  • Employees using the ‘View My Information’ button can no longer view the time location report and the departmental wages report.

Additionally, Time Clock MTS Version 2.3.1 (released about a month ago) included a fix for the shift restriction feature which was working for a long time and then stopped working.

Version 2.2.9 and 2.2.10 Released

A couple of minor releases in the last few days fixing up some small problems and putting in some new logging code to try to track down some errors that have started surfacing for some reason.

Version 2.2.9

Fingerprint support was re-enabled and the method used to check for correct fingerprint driver installation was changed. This is the resolution to the hard crash that was fixed up in the last release. There were also a couple of minor feature changes including adding last 14 days selection to the edit times screen and allowing administrators to setup web camera image capture on a client by client basis.

Version 2.2.10

A fix to the type 13 mismatch error that was caused by the release of Version 2.2.10. I’ve also added a bunch of new logging code to try to track down why people are suddenly (and mysteriously) getting Element Not found Errors. This is particularly baffling because this area of the software has not been touched in well over a year.

Version 2.2.7 and 2.2.8 Released

Many apologies for the two releases so close together, but it was critical to release version 2.2.8 due to a hard crash that some users were seeing.

Changes for version 2.2.8:

  • Fix to hard crash that some users were seeing. Root cause was the fingerprint scanner support. For the time being fingerprint support has been disabled. It will be re-instated within 24 hours.

Changes for version 2.2.7:

  • Added support for logging to an Excel worksheet. This can be enabled by running Time Clock MTS with the command line parameter ExcelDebug
  • Fixed a problem where the password was not being reset correctly during the 30 day trial period
  • Made various changes to allow easier recovery of forgotten or lost administrator passwords. Lots of users seem to lose them and I want to make sure this isn’t a programming issue with the software.
  • Employee image capture can now be setup on a client by client basis. Previously it could only be setup if the administrator PC had a webcam on it.
  • Fix to the view information button to require a finger scan when fingerprint security is activated.

Version 2.2.6 Released

New release today that changes the way that Digital Persona Fingerprint scanner support is handled. Previously the install files for the fingerprint scanners were included in the general install file but this had beefed the install file to nearly 11 megabytes. In my opinion this was entirely too large and was probably leading to a lot of failed downloads. The fingerprint scanning feature is excellent but is currently only used by a small number of companies so I’ve decided to make support optional and not make the download excessively large for everyone. So, Time Clock MTS now detects if fingerprint support is installed when you try to access any of the fingerprint features within the software and prompts you to download and install the fingerprint scanner install files. Hopefully this will make things a lot easier for new users of the software and help improve download speeds and success rates.

I’ve been a bit remiss posting entries here when I’ve uploaded new versions lately so I’ll just cover the changes to the last few versions quickly (because they’ve been very minor).

Version 2.2.5

Version 2.2.4

  • Fix to problem with adding employees to the database for people who had installed the update file, problem was caused by release of version 2.2.3.

Version 2.2.3

  • Reworked all of the code that updated the Time Clock Database when upgrading to a new version of the software. Tested to make sure that MS SQL and MySQL databases were updated properly back from version 1.7.3.

Version 2.2.2

  • Fix to minor vacation / sick time rounding problem.

NTP Time Server Problem Fixed

As I mentioned in my last post the time servers

time-a.nist.gov, MD USA
time-b.nist.gov, MD USA

appear to have stopped to responding for time requests in the format that Time Clock MTS requires. I have released a new version of the software (version 2.2.5) that swaps out these two servers for two new ones that do work. The new servers are:

nist1.uccaribe.edu in Puerto Rico
nist1-ny.WiTime.net, NY USA

If you are having troubles with your time server and dont want to bother with the fix I suggested in the last entry then just update all your admin and client version of Time Clock MTS to the latest version and you should be up and running.