This warning appears when you do the following:

1) Launch AP, GL, IC or any module that will cause a conflict with Purchase Orders for Adagio (POA) dayend (including launching POA on a separate workstation)

2) Attempt to run POA dayend processing, resulting in a warning "Day End requires exclusive use of this data set..."

3) Close the warning but keep POA open

4) Attempt to launch Adagio JobCost

I'm not sure whether this is an issue with POA or JobCost. I'm wondering whether someone in tech support could replicate this and let me know.

I am using the latest JC 8.1A (071029) and POA (080806).

Exiting POA and re-launching it resolves the conflict, but one shouldn't have to do that.

Steve Schwartz

Hi Steve,

If closing POA prior to attempting to launch JobCost does not reveal any error - as you found - then the issue lies with POA. A multi-user resource or perhaps another file that was locked by the POA Day End was not correctly released when the 'exclusivity' test failed. I assume that nothing else in POA was open; no functions but just the application.

I don't have POA installed so I cannot attempt to replicate this.

I was afraid you were going to say that.

Can you forward this topic to the POA people for their reaction.

Thanks

Steve

Hi,
I believe the message or locking is caused by POA with respect to End of Day Processing. POA creates a Job Cost batch directly into Adagio Job Costing (not manually retrieved), and the exclusive locking of the batch processing in job costing is the cause of the reported message. As soon as the EOD is completed, the locking should be released.
Brian

Hi Brian

I don't think you read what I wrote. EOD cannot be completed because there are users in the system. Just the act of attempting to run EOD locks up JobCost, even after you click out of the failed attempt.

Steve