Gradience Pro / Enterprise - Odd Performance

If your Gradience software is performing oddly, you should suspect database corruption. Typically, you would run the Gradience database maintenance tool at the server/machine hosting the data and in nearly all cases the corruption can be removed. However, when the corruption is caused by different versions of Gradience that are all touching the same data, the ability of this tool to remove the corruption drops to a 50/50 coin toss.

If the corruption cannot be removed, the bad software performance cannot be resolved. This leaves you only one option, which is to restore a backup that was made prior to the bad software performance. You would then have to re-enter any data now missing between then and now.

So, whatever version number you are running, please ensure that you have the same [release] running on all computers that have Gradience installed

At this writing, the latest version is 11.0.1606.29, which came out on June 29, 2016 but by the time you read this, we may have released a newer version.

This is how the versioning works...

The 16 refers to the year 2016.
The 06 refers to the month of June.
The 29 refers to the day-of-the-month.

To find your full, multi-digit version number, please click Help > About in your software. You should do this at each workstation running Gradience as well as at the server if the database is located there. 

Each computer where you have Gradience Attendance, Records, TimeClock, and FMLA Tracker installed MUST be running the [SAME] multi-digit version number. 

Click here to update to the most recent version.

Click here for the steps to remove database corruption.





Have more questions? Submit a request



Article is closed for comments.