Browse lookup
GCC Consulting
gcc at optonline.net
Thu Dec 16 08:21:03 PST 2004
> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com
> [mailto:filepro-list-bounces at lists.celestial.com] On Behalf
> Of Kenneth Brody
> Sent: Thursday, December 16, 2004 10:47 AM
> To: rkreiss at gccconsulting.net
> Cc: 'Filepro 2 List'
> Subject: Re: Browse lookup
>
> GCC Consulting wrote:
> [...]
> > > is there any reason you couldn't check for "not foobar" to see if
> > > the lookup didn't get a record?
> > >
> >
> > Here is the processing in question. Are you indicating that Not
> > postar could be inserted at line 97?
> >
> [...]
> > 96 ------- - - - - - - - - - - -
> - - - - -
> > â If:
> > Then: lookup pros = postar k=1 i=1 -nxm b=(ba&bb&bc)
> [...]
>
> If this were a regular (ie: non-browse) lookup, how would you
> check for the success/failure of it? You would test "not
> pros". Just because this is a browse lookup does not negate
> that ability.
>
> Yes, you do a partial check on the next line:
>
> > 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.)
Ken,
Thanks for the heads up no not .....
However, the @sl="BRKY" is not really redundant. I have found that most Windows
users are in the habit of hitting the ESC key when they want to cancel
something. So, I trap both pressing X or ESC to cancel the operation. Yes, I
could turn off the break key but this is just as easy.
In this case, I still have to trap for the error when <S> is pressed. I don't
want the rest of the processing to run.
However, adding -s and a not statement will preclude doing a lookup first to
check for valid records first.
Richard Kreiss
GCC Consulting
More information about the Filepro-list
mailing list