Can a BRW LOOKUP be done on a -v table or out processing

[Richard Tartaglia]

--- "Brian K. White" <brian at aljex.com> wrote:

> 
> ----- Original Message ----- 
> From: "Richard Tartaglia" <fp_rich at yahoo.com>
> To: "FP List" <Filepro-list at lists.celestial.com>
> Sent: Thursday, October 13, 2005 8:55 AM
> Subject: Can a BRW LOOKUP be done on a -v table or
> out processing
> 
> 
> >I am trying so select a name from one FP file while
> > printing a report from another file.
> >
> > There are lists of names in each record of one
> file.
> > The names are associated with other data in that
> file.
> > There is a corresponding name file to make sure
> names
> > are all spelled the same in each record.
> >
> > I am trying to print a report based on a name. I
> would
> > have to look-up into the name file and set that
> name
> > in a -v table or output processing. I have tried
> both.
> >
> > I have looked but can't find if BROWSE look-up
> will
> > work in ether the -v table of output.
> >
> > When I run processing, the line with the look-up
> is
> > TRUE but it falls through to the next line. I just
> > need to know if I am trying something I shouldn't
> be
> > or if I have gone completely mad and can't write
> code
> > anymore.
> 
> 
> The lookup itself isn't true or false. You may have
> something on the If: of 
> the lookup line to decide if you want to do the
> lookup or not, but I doubt 
> you have or want that here.
> 
> the very next line needs to have the
> if: not dict
> then: gosub fixname  'name wasn't found in
> dictionary
> if:  ' name was ok or has been fixed up by gosub
> then: return    'assuming we were already in a
> "ckname" gosub
> 
> gosub fixname will have the same lookup but with
> browse enabled
> the first lookup will not have browse, it's only
> purpose is to find an exact 
> match or fail.
 
Brian 

You are right, there is no if statment on the look-up
line. I was just making sure the line itself eas being
exicuted. 

I am using a key field lookup to an index and seting
the key to "A" prior to the look-up. The lookup is set
to get the next higher match.

Richard