records not locking?

[scooter6 at gmail.com]

Okay - after some more digging.....if I pull a record up directly in the
filePro file itself and am in update mode...and then try to pull the
account up in the processing that does all the lookups and protected
lookups, I get 'Wating for 'mainfile' record xxxxxx to be unlocked'
But, if I pull up the record in the processing that does all the lookups
and what the employees use to access the main file, it lets me pull it up
with no problem?



On Wed, Apr 16, 2014 at 1:33 PM, Kenneth Brody <kenbrody at spamcop.net> wrote:

> 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
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20140416/14349a5d/attachment.html