SYMPTOM:

Let us visualise a few gloomy, unforeseen instances.

1. There is power failure while Payroll Generation is on its way.

2. Your System crashes. You restart the Application, and proceed for normal works. However, all of a sudden, the System blocks with a message, like "The option is being used at some other terminal. Please try after some time". However, you are dead sure that, there is none other than yourself, who may be accessing the option.

Or, let us assume that just before your System terminated abnormally, you were making some modifications on an Attendance Class. After restarting the Application - as you attempt to modify that Attendance Class - you are stuck with   a message, like "This Attendance Class is being used at some other terminal. You cannot proceed with it or any of its details".

CAUSE:

PERKS, as a Multiuser software, ensures data security from concurrent accesses. Imagine, if indeed, two persons were allowed to access and modify the same Attendance Class (or, some other such entity)! In all probability, the person, who saves the data last, would emerge as the 'Winner'.    

To avoid such 'races', the System blocks all the following user(s), who access the option. To accomplish that, the System, internally, keeps a track of who is doing what (even if you are not using the 'Activity Log' / 'Audit Trail' feature).

When the  System crashes, its internal log goes out of tune with the actual scenario. The inevitable result is that, you would encounter the 'blocking' messages.

RESOLUTION:

After any abnormal termination, instead of starting your work right away, you are always advised to make use of the 'SRESET' utility. Press, the 'Start' button on the taskbar of your desktop, and choose the Program folder for PERKS. You will observe a shortcut in the label of Reset System Files. Proceed to clear the 'zombie' users.