PFCHECKLOCK (was RE: am I missing traffic?)

[Jeff Harrison]

--- George Simon <GSimon at americanriverintl.com> wrote:

[snip]

> Well, in the interest of keeping some traffic
> moving, I'll post a
> question that I asked Ken a couple of weeks ago, but
> never received an
> answer.  Maybe he never got my message.
> 
> Native filePro 5.0.14 r/dclerk
> When running with PFCHECKLOCK=ON and doing a
> protected browse lookup
> with browse processing, if an  assignment is made to
> the records as they
> pass through the browse processing, I get the
> message saying that I'm
> making an assignment to an un-protected record. 
> This did not happen
> with version 5.0.09.
> 
> Is this a bug introduced after version 5.0.09 or is
> it that we are no
> longer supposed to assign values to a record through
> browse processing?
> _______________________________________________

In my opinion it is not a good practice to do what you
are suggesting.  I don't believe that browse lookups
were designed for what you are doing.  I would change
all the browse lookups to read-only, and have a
separate routine (that utilizes a standard protected
lookup in a loop) that does the updates that you need.

Good Luck

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHImport and JHExport. The fastest and
easiest ways to create code for filePro Imports and
Exports. 



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com