Protecting browse lookup records

[GCC Consulting]

> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com 
> [mailto:filepro-list-bounces at lists.celestial.com] On Behalf 
> Of Mike Schwartz (PC Support & Services, Appleton, WI)
> Sent: Wednesday, March 16, 2005 10:46 AM
> To: FilePro List
> Subject: Protecting browse lookup records
> 
>      I could probably test this, but I'm hoping somebody has 
> a quick answer:
> 
>      Generally, I don't have much need to use the "P" option 
> to protect browse lookups, but I'm looking at a lot of 
> filepro code at a customer site where they *always* protect 
> *every* lookup; even lookups to a "free" record, (which 
> shouldn't be necessary).
> 
>      In filePro (any current version), when I use the P flag 
> to protect a browse lookup of, say, 14 lines, are all 14 
> lines showing in the window protected (and locked from other 
> users) while the browse window is up on the screen?  Or, is 
> only the record the cursor is on protected (and locked).
> 
> Thanks,
> 
> --
> Mike SchwartzRichard Kreiss
GCC Consulting 
> PC Support & Services
> 3650 N Suncrest Lane
> Appleton, WI 54914
> 
If I am recalling correctly, you are locking ALL of the records in the browse
window.  The only time it is necessary to lock a record would be if you were
updating or posting to it.

In that case, I usually put record # into a dummy field and then do a protected
lookup using the record #.  This just locks that record for the time it is being
updated.

Ken has said the lookup free locks that record (an implicit -p).