Lookup syntax - literal key

[Bruce Easton]

Kenneth Brody wrote Friday, September 07, 2007 3:43 PM:
> To: Jay R. Ashworth
> Cc: filepro-list at lists.celestial.com
> Subject: Re: Lookup syntax - literal key
> 
> 
> Quoting Jay R. Ashworth (Fri, 7 Sep 2007 15:01:16 -0400):
> 
> > On Fri, Sep 07, 2007 at 12:03:54PM -0400, Kenneth Brody wrote:
> >> >Does "expression" not devolve as far as "string literal"?
> >> >
> >> >Or is this really complaining about the brw= argument?
> >>
> >> Well, that is where it's pointing.  :-)
> >>
> >> Shouldn't that be:
> >>
> >>     b="*2"
> >
> > In fact, that didn't help either.
> 
> Your original:
> 
>      lookup code=svalookr k=("CAT") i=A -nx brw="*2"
> 
> gives me a syntax error, with the carat on the "w" of "brw=", exactly
> as on your system.
> 
> The following passes syntax here:
> 
>      lookup code=svalookr k=("CAT") i=A -nx b="*2"
> 
> (I haven't tried actually running it, as I have no file set up for it
> to look up into with this exact syntax.)
> 
> Can you explain exactly what happened on your system with simply changing
> the "brw=" to "b="?
> 
> [...]
> 
Yeah, there aren't a lot of possibilities here.  Since he has
a non-variable file, then some sort of browse should be coming up
if, in fact, he has that syntax at the end of b="*2".

Even if there were no records in the lookup file or even if
there was only one field in the lookup file, it still paints 
a browse.

Whilst I was writing this, Jay wrote back to Ken:

>  >   lookup code=svalookr k=("CAT") i=A -nx b="*2"

> Here, it didn't work.  I got a syntax error on that as well.

Jay - there should be no syntax error coming from that kind 
of line.  Where does it point to in the line?  What
version of filepro are you running?

Bruce

Bruce Easton
STN, Inc.