Hi Support:

Lately, I have seen users calling that their Adagio froze or they cannot enter a document after a crash. I identified the issue as clicking the Print button or the Post button still having the batch opened.

Currently, users have bigger monitors and even two monitors. They move the open batch document list besides the batch list grid. Then without closing the batch, they click on the Print button for the batch instead of the print button for the document. Also, the batch list might be minimized and they click on the Post button without closing the batch.

The post issue needs to be solved with a Data Integrity Check.

Could R&D verify that the batch has been closed before allowing clicking on those buttons?

Attached an example

Hi Support:

Patricia's post started me wondering because I have seen unexpected results occasionally.

Using Payables 9.3C I tested both Invoice and Manual Cheque entry. In both cases, I opened batch ## from the Batch List. While the Entry list for that batch was open, I clicked on Print, Listing and Post buttons on the main Batch List window.

Invoices:
Both the Listing and Post buttons correctly said that "Batch ## is already open". Neither function proceeded further and operation seemed unaffected.

Manual Cheques:
Both the Listing and Post buttons correctly said that "Batch ## is already open". Neither function proceeded further and operation seemed unaffected.

However the Print button was different. It correctly said the batch was open. But none of the buttons from the Entry list screen would work after that. All returned an Access Violation message. It almost seemed as if the data tables were closed.

My tests sound a little different from Patricia's in that I didn't find that a Data Integrity Check was necessary.

Thank you both for your feedback.

I will have R&D investigate for future releases.

Hello Bruce and Patricia,


This has been fixed in the Payables 9.3C (2023.03.15) Hot Fix just released.