Re: ACR500 Record Lock -- BPCS-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Don't know if it applies to your version, but I seem to remember that
ACR500 had the nasty habit of updating the payment type with a ';'
(RAR.ARPTYP) when a session ended abnormally, which meant it was locked
for processing.

-----Original Message-----
From: bpcs-l-bounces+tony.cregg=essentialfinance.net@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+tony.cregg=essentialfinance.net@xxxxxxxxxxxx] On
Behalf Of daparnin@xxxxxxxxxxxxxx
Sent: 29 February 2008 22:16
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] ACR500 Record Lock

A user accidentally killed a session while in ACR500. Now when we try
to
do a payment we get the message: "Attempting to access a record that is

in use by another job. Try again" with a message ID of UMI1014. I've
looked at the code and it appears that message only is displayed if the
program can't chain to get a record in a handful of files. I don't see
any record locks. Could the program have deleted a record when the
session died? They are trying to close things up because today is
month-end.

We are on BPCS 4.02. Thanks.

Dave Parnin

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.