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.