Post by Admin on Jul 10, 2017 10:52:07 GMT 12
Suppose you are doing a bank reconciliation on one PC and someone on another PC was to start the Enter Bank Statement Details (EBSD) on another PC or edit a receipt that was in you reconciliation. If this happened you'd expect there to be some peculiar results.
To prevent this sort of clash, processes like EBSD and Generate Payments write a "batch" record to warn other users off and prevent the clash and there will be a message like this:-
But occasionally, you'll get this message when there is no one else on the system. This happened to one of our users just the other day. There was a little head scratching and then it was mentioned that there had been a power cut while working on the bank reconciliation. This had left the batch record in place, preventing users from running almost anything.
The problem is easily fixed. If you are sure that no one else is on the system, do the following:-
To prevent this sort of clash, processes like EBSD and Generate Payments write a "batch" record to warn other users off and prevent the clash and there will be a message like this:-
- 'This operation can not be completed because:-...'
But occasionally, you'll get this message when there is no one else on the system. This happened to one of our users just the other day. There was a little head scratching and then it was mentioned that there had been a power cut while working on the bank reconciliation. This had left the batch record in place, preventing users from running almost anything.
The problem is easily fixed. If you are sure that no one else is on the system, do the following:-
- On the main menu select "Admin"
- On the sub-menu select "Utilities"
- On the next menu select "Close a batch"
- Check the message and click <OK>