Record is being update-Access denied message

[Kenneth Brody]

Quoting Jay R. Ashworth (Fri, 25 Aug 2006 11:25:49 -0400):

> On Fri, Aug 25, 2006 at 10:22:14AM -0500, Rick Mitchell wrote:
> > From: "Don Coleman" <dcoleman at dgcreact.com>
> > > Windows 2000 Advanced Server, WINXP & WIN2000 clients, fP v5.0.13
> > >
> > > My client has found one record in a file which messages "record is
> > > being updated-access denied". Last night they rebooted their server
> > > and they are still getting the message today. While it is possible
> > > someone is back updating this record I would find it unlikely. Do I
> > > have any other options for gaining access to this record?
> >
> > kill the lockfile.
>
> Well, in my experience, that message doesn't *come* from the lockfile;

You are correct.  As I have stated repeatedly on this list whenever
someone mentions "remove the lockfile" for clearing record locks...

    The lockfile has absolutely nothing to do with record locks.
    Nothing.  Nada.  Zip.  Zilch.

The lockfile is for inter-module locking -- something which record
locks cannot do.  For example, prevent someone from building a new
automatic index when someone is in *clerk in the file.

> record level locks are maintained in the kernel lock table, and
> usually, a reboot should clear up the problem.

If a serverreboot doesn't clear the locks, something is very wrong.

> Is it possible they have an overnight cronjob that runs something and
> has gotten stuck on a record?
>
> Run (or get and run) showlock, and see what it says.

As someone else pointed out, this is Windows, and even sysinternals.com
doesn't have any showlock-like utility that I can see.

However, that doesn't mean that another workstation can't have locked
the record since the reboot.

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