-p on LOOKUPs - further clarification?

[Kenneth Brody]

Quoting Jay R. Ashworth (Mon, 18 Jun 2007 15:01:57 -0400):

> On Fri, Jun 15, 2007 at 04:10:36PM -0400, Bruce Easton wrote:
[...]
> > The lookup with the -p indicates that the record is locked as soon
> > as it is accessed, not while it is writing.  If the record is already
> > locked, then filepro will wait until the record is unlocked before it
> > accesses it for writing by someone else.  (See the description of -w
> > flag in online help for another option with different behavior.)  In
> > regards to the effects of the "write" command, as Jeff indicated,
> > also see the "close" command.
>
> Yeah, but that doesn't get to the heart of what I was after: will a
> lookup -P on *one* tag to a file block a lookup -P on a *different* tag
> *to the same file*, in a given table?
>

You can see for yourself with a simple experiment:

     lookup foo = filename r=("1") -p
     mesgbox "First lookup done.  See what showlock says."
     lookup bar = filename r=("2") -p
     mesgbox "Second lookup done.  See what showlock says."
     lookup baz = filename r=("3") -p
     mesgbox "Third lookup done.  See what showlock says."
     write bar
     mesgbox "Second lookup written.  See what showlock says."

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