PFCHECKLOCK (was RE: am I missing traffic?)

[George Simon]

That's the answer I was looking for.
Thanks.

-----Original Message-----
From: filepro-list-bounces+george=worldest.com at lists.celestial.com
[mailto:filepro-list-bounces+george=worldest.com at lists.celestial.com] On
Behalf Of Kenneth Brody
Sent: Tuesday, September 12, 2006 3:09 PM
To: filepro-list at lists.celestial.com
Subject: RE: PFCHECKLOCK (was RE: am I missing traffic?)

Quoting Kenneth Brody (Tue, 12 Sep 2006 15:02:27 -0400):
[...]
> > This processing worked fine with version 5.0.09 and all previous
> > versions of filePro.  What changed with version 5.0.14 that now the
> > same processing gets the warning message?
[...]
> I would have to check, but the change is probably just better
detection
> of writing to an unlocked record.  Remember, just because the lookup
> has a "-p" flag doesn't mean that the record is locked at the time you
> make the assignment.  (For example, after a WRITE.)

Quoting the 5.0.14 readme:

(All) #681

    PFCHECKLOCK didn't pick up some unprotected writes in browse
lookups.

--

_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list