Browse lookup

[Kenneth Brody]

Keith F Weatherhead wrote:
[...]
> >>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.
> >
> > 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.
> 
> While I understood Kens point, like you I always use the two lines
> to handle them seperately.  I suppose you could have a error handler
> for failed browse lookups and at that point check if you got there
> with: @sk eq "BRKY", rather than a "no find" condition.  In most
> cases, you may very well have to handle the situations differently
> anyway, just which method works better for your style of programming.

If you want to treat "failed because of no records" and "failed because
the user broke out of the browse" differently, then the BRKY test is
obviously not redundant.  However, based on the OP's code, it appeared
that there was no difference in treatment.

-- 
+-------------------------+--------------------+-----------------------------+
| Kenneth J. Brody        | www.hvcomputer.com |                             |
| kenbrody/at\spamcop.net | www.fptech.com     | #include <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------------+
Don't e-mail me at: <mailto:ThisIsASpamTrap at gmail.com>