browse lookup - spped up selection

[Kenneth Brody]

Quoting Dennis Malen (Fri, 14 Apr 2006 13:11:10 -0400):

> Ken,
>
> I do use the drop command.
>
> Are you saying that you can create a selection set in a file and use
> that selection set name as you wish in any processing and if it does
> not match it will be dropped.

You can put a selection set name on the "if" line, and it will evaluate
that selection set.

> If that is the case that is virtually unknown by most people that I
> know (I probably don't know the right people.) Please note I am still
> on 4.8.

This has been available since 1.0, so 4.8 isn't a problem.

> In any event, even if you can do that, I don't think that satisfies my
> speed issue as it still has to go through processing and if there is no
> match drop the record.

Well, if the selection set isn't suffucient, then the only thing you can
do is make your processing more efficient.  How else can you tell filePro
to drop records from the browse window?

> In my drop processing I am going through 5 conditions to determine if
> the record should be dropped. Will your approach speed things up?

Perhaps.  It depends on the 5 conditions, how often it's the 5th one
that drops the record versus the first, how well you've written your
processing, how well you write the selection set, what percentage of
records are dropped versus included, and so on.

> Also when I use:
>
> If: not selectionname
>
> do I use the full name "sel.selectionname" or just "selectionname".

If you needed the "sel." I would have said so.  (Not to mention that
if it were needed, that would mean re-writing it for Windows, where
it's a ".sel" extension.)

Just like you don't need "prc."/"tok."/etc for CALL/CHAIN, or "out."
for FORM, or wherever else you might refer to a filePro format file
in processing, you don't include the prefix/suffix.

[...]

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com