-p on LOOKUPs - further clarification?

[Kenneth Brody]

Quoting Jay R. Ashworth (Fri, 15 Jun 2007 14:42:12 -0400):
[...]
> So, when you say -p, filePro write locks the target record (and
> associated index records) *while it is writing that data item* -- and
> unlocks it automagically afterwards?
[...]

A "lookup -p" time:

    The lookup is performed, and the record is located.

    The record is locked.

    The record is read.

... The record is used by processing. ...

When it's time to write/unlock the record[*]:

    The record is written.

    The record is unlocked.


[*]  Lookup records are written:
        At an explicit WRITE.
        At an explicit CLOSE.
        A GETNEXT/GETPREV is executed.
        The LOOKUP itself is re-executed.
        When processing ends.  Note that field-level events (such as
            @WLF/@WEF) ending do not constitute "processing ending".

     (This list is from memory, so it may be incomplete.)

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