Can't run reports because file locked?

[Kenneth Brody]

Quoting Dan Snyder (Thu, 8 Sep 2005 11:12:47 -0400):
[...]
> If personA (anyone) goes into a specific filePro file (psales) using
> "B-Inquire, Update, Add" and then personB (anyone else) tries to go into
> "D-Request Output" for that same file personB will get the following
> error message.
>     *** A filePro Error Has Occurred ***
>     Inquire, Update, Add Function Running On This File
>     File not available.
>     Somebody else is modifying the file;  try again later.
>
> PersonA is not doing an add or update, they are simply doing an inquiry.
> If I delete the lockfile personA can get into the file in question.

Rule #1:  Never remove the lockfile while the file is in use, unless
you like getting "help, our file is corrupted!" calls in the middle
of the night.

[...]
> I have tried to use the "showlock" utility and Bob Stockler's lock.info
> shell script at <http://www.hvcomputer.com/download/public.html>
> http://www.hvcomputer.com/download/public.html to figure out what is

Rule #2:  Record locking and the lockfile have nothing to do with each
other.

[...]
> Does anyone have any idea what is causing this or how to fix it?

If you want to allow the report to run while others are in *clerk,
include the "-u" flag on the *report command line.  That's what it's
there for.

[...]

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com