-p on LOOKUPs - further clarification?

[John Esak]

>
> 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?
>
> Cheers,
> -- jra

If I'm understanding this question... no it would not. Why would it?
These -p locks are "record" sensitive and related... not file based...

If your question were a little more specific... meaning if you're asking
what I'm guessing you're asking... will a -p lock on one alias to one record
*block* the ability to do a lookup -p with a different alias to the same
record.  *fi* that is waht you were asking... hold on... I'll try it...
should take about 60 seconds to write and test....



  1  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
       Then: end
  2  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -
@keyT  . If: '@keyT
       Then:
  3  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
       Then: lookup one=test r=("1") -p
  4  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
       Then: mesgbox "no prolbem so far"
  5  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
       Then: lookup two=test r=("1") -p
  6  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
       Then: mesgbox "still no problem..."
  7      If:
       Then: end


If you were to run this... you would see that it passes just fine.  Why?
Because, *you* own the lock on the record, so nothing is going to prevent
you from doing something to that record... like locking again with a
different alias if you want to... but I can't see the programming reason for
doing this.

John Esak