Browse lookup

[John Esak]

> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at bestweb.net]
> Sent: Friday, December 17, 2004 9:40 AM
> To: john at valar.com
> Cc: filePro mailing list
> Subject: Re: Browse lookup
>
>
> John Esak wrote:
> >
> > >
> > > >  97  -------   -   -   -   -   -   -   -   -   -   -   -   -
> > > -   -   -   -
> > > >         —„ If:         @sk="BRKY" or  @bk = "X"
> > > >        Then:         GOTO is_exit
> > >
> > > This will check for breaking out or pressing 'X', but it doesn't check
> > > for the lookup having failed because there were no records.
> Simply add
> > > "or not pros".  (Actually, in that case, the check for BRKY
> is redundant.)
> >
> > Just curious, why is the test for @BRKY redundant here??
> [...]
>
> Because if you press BREAK in the browse lookup window, it will cause the
> lookup to fail, making the BRKY test redundant once you add the "not pros"
> test to handle the "there are no records" situation.
>
> --
> +-------------------------+--------------------+------------------
> -----------+
> | Kenneth J. Brody        | www.hvcomputer.com |

Ah, I never understood it that way. I always put the @sk eq "BRKY" test
above the "no record" test. I don't know why... In any case, I hear what you
are saying about it causing the lookup to break.  In either case, I consider
the two situations completely different and put the @sk test first so that
both situations can be handled independently.

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.6.0 - Release Date: 12/17/2004