records not locking?

[Kenneth Brody]

On 4/16/2014 12:23 PM, Howard wrote:
> What I mean is if you then make an assignment to that record it will not
> re-lock it.
> Yes if you re-lookup the record with a lock I think it will work but:
> out(14)="Y"
> write out
> out(20)="1234"
>
> Will leave the record from the lookup "out" unlocked and someone can go
> into clerk and update it too.
[...]

I'll have to see what happens here with that, as the second assignment 
should have filePro re-lock the record.

Note, however, that even with filePro re-locking the record, the above 
construct is a "bad idea", as the record is unlocked between the WRITE and 
the next assignment to that lookup, and nothing stops another process from 
grabbing and updating the record in the time.  It's the equivalent to 
executing an unprotected lookup and then assigning to it.

-- 
Kenneth Brody