False Assigning to lookup field without a lock error messages

[Scott Walker]

-----Original Message-----
From: Kenneth Brody [mailto:kenbrody at bestweb.net] 
Sent: Thursday, April 13, 2006 7:36 PM
To: Scott Walker
Subject: RE: False Assigning to lookup field without a lock error
messages

Quoting Scott Walker (Thu, 13 Apr 2006 19:06:41 -0400):
[...]
> 	The three lookups to otscust1 are listed below.  All are
> protected.
>
>
> 	lookup bill1 = otscust1 k=l i=c -npx
> 	lookup bill2 = otscust1 k=3 i=a -npx
> 	lookup bill2 = otscust1 k=m i=c -npx
>
> When I run the process, I get:
>
> 	"Assigning to lookup field without lock."
> 	"Mainfile=otscustcodechg, lookfile=otscust1, prc=chgbill,
> line=469"
>
> This would seem impossible given the above lookup statements which are
> the only ones in this prc table that do a lookup to otscust1 file.

Ken asked:


Have you released the lock via a WRITE, sometime between the lookup
and line 469?


Ken,

No, the only time I use "write" on this file is a couple of lines AFTER
line number 469.  

The only thing that perhaps is a clue on this false error message (that
I can think of):


	The actual lookup statement is done much earlier in the
processing table to see if the Customer Code exists.  Then much later in
processing, after many intervening lookups, in a totally different
subroutine, I assign some values to a couple of the fields in the
otscust1 file using:

	bill1(1)=3


Then I write & close:

	write bill1

	close bill1


(BTW...I know that's overkill but this code goes back to 1988.)

Of course, it's on the bill1(1)=3 line that I get what I feel is the
false error.

Ken, thanks for your help on this.  It's not causing me a problem so
please don't worry about it.  I'm just gonna put PFCHECKLOCKPOPUP=OFF on
the menu script for this program and let it go at that.


Regards,


Scott