odd lookup problem

[Richard Kreiss]

New problem:

Doing a lookup in the auto processing table using lv=master_code&"99" to
display information from the sales journal in the current file.  The NOT
sales line shows false when a record is present in the sales journal.

When @keyW is pressed and this lookup is done from input processing, the NOT
sales is true.

I removed the casting lv from the input process as a test but NOT sales
still showed as true in input processing.

My question is, why would the lookup return the correct value in auto
processing but not in input processing.

Richard

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Kenneth Brody
> Sent: Tuesday, November 09, 2010 2:20 PM
> To: rkreiss at gccconsulting.net
> Cc: Filepro-list at lists.celestial.com
> Subject: Re: odd lookup problem
> 
> On 11/9/2010 2:01 PM, Richard Kreiss wrote:
> [...]
> > I think that when using either next lower or next greater, the NOT
> FILENAME is necessary as it is possible that the lookup would be passed
the
> last value in the index or before the first value in the index.  Although
in this
> real world case, there are records on either side of the lookup value.
> 
> Of course you need to have a test for success on any lookup, unless you
> don't mind a fatal filePro error if you try accessing a field from a
failed lookup.
> A "-nl" or "-ng" lookup is no different in this regard than a "-nx"
> lookup.
> 
> This can be done with either:
> 
>      if:  not lookupname
>    then:  handle failure
> 
> or
> 
>      if:  lookupname
>    then:  handle success
> 
> --
> Kenneth Brody
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list