I need your help. I have a client on a network install running current versions of Ledger and Payables with plenty of lanpacs. Even though we have set up the shortcut to run Financial Reporter separately from Ledger we are still getting the message "Financial Reporter is running..." when we try to post a batch. We have checked and only one user is in Financial Reporter (the controller). I cannot duplicate this scenario in our own network install.

Any ideas?

Hi, Lyndon,

From the release notes and Readme help for GL9.2A(150903):

"In Ledger 9.2A, posting or unposting batches on a station while the Financial Reporter was open on the same station, at the time as users were in Ledger on other stations, in some cases caused data integrity errors. You can no longer post while the Financial Reporter is open on the same station. If you attempt to post the warning “Financial Reporter is running, you must close it first. Use ALT-TAB to switch to it.” will be displayed."

I suspect this is what they are running into.

...so this is a step backwards then? Without FX there is no way for a controller to monitor operations without preventing the finance department from doing their work?

Hi Lyndon:

I'm curious. The Readme files says that "You can no longer post while the Financial Reporter is open on the same station." To me that means if the Controller has the Financial Reporter open, he or she would be unable to post but that others would be able to post.

Reading between the lines of your post, it seems like the user trying to post the batch is not the Controller. is that correct?

They cannot be open on the same station. They can be open on different stations.

So what you are saying is that if the controller has ONLY Financial Reporter open and thee other users on their own workstations are using Ledger and Payables, the error will not appear?

I'm saying that the Ledger and Financial Reporter cannot be open on the same station that is trying to post the batch.

Thanks Andrew. Will this be resolved in a future release? We have a number of clients that this affects.

We think it's a Microsoft problem. We are investigating alternative strategies.

Does anyone have experience with this on a remote desktop server? Would it be correct to assume all the connected users are on the same "station" for the purposes of this restriction?