browse lookup - spped up selection

[Howard Wolowitz]

Top Posted

Yes BUT the selection set is looking at the current record - the one you are 
sitting on - NOT the record presented buy the browse.  Therefore it is 
useless, unless your browse is a lookup - which cause many many problems and 
is slow to boot.

Howie

----- Original Message ----- 
From: "Dennis Malen" <dmalen at malen.com>
To: "Howard Wolowitz" <howiewz at beonthenet.com>; "Kenneth Brody" 
<kenbrody at bestweb.net>
Cc: <filepro-list at lists.celestial.com>
Sent: Friday, April 14, 2006 1:47 PM
Subject: Re: browse lookup - spped up selection


> Fortunately for me in this instance, I am in the same file.
>
> Dennis Malen
> ----- Original Message ----- 
> From: "Howard Wolowitz" <howiewz at beonthenet.com>
> To: "Dennis Malen" <dmalen at malen.com>; "Kenneth Brody" 
> <kenbrody at bestweb.net>
> Cc: <filepro-list at lists.celestial.com>
> Sent: Friday, April 14, 2006 1:19 PM
> Subject: Re: browse lookup - spped up selection
>
>
>> Top Posted
>>
>> The problem with using a selection set inside a browse processing routine 
>> is that the selection set always refers to the current record in the 
>> current file so I have never found a way to make it useful.
>>
>> Howie
>>
>>
>> ----- Original Message ----- 
>> From: "Dennis Malen" <dmalen at malen.com>
>> To: "Kenneth Brody" <kenbrody at bestweb.net>
>> Cc: <filepro-list at lists.celestial.com>
>> Sent: Friday, April 14, 2006 1:11 PM
>> Subject: Re: browse lookup - spped up selection
>>
>>
>>> 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.
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> In my drop processing I am going through 5 conditions to determine if 
>>> the record should be dropped. Will your approach speed things up?
>>>
>>> Also when I use:
>>>
>>> If: not selectionname
>>>
>>> do I use the full name "sel.selectionname" or just "selectionname".
>>>
>>> Thanks,
>>>
>>> Dennis Malen
>>> 516.479.5912
>>> ----- Original Message ----- 
>>> From: "Kenneth Brody" <kenbrody at bestweb.net>
>>> To: "Dennis Malen" <dmalen at malen.com>
>>> Cc: <filepro-list at lists.celestial.com>
>>> Sent: Thursday, April 13, 2006 6:54 PM
>>> Subject: Re: browse lookup - spped up selection
>>>
>>>
>>>> (Top-posting corrected.)
>>>>
>>>> Quoting Dennis Malen (Thu, 13 Apr 2006 18:26:56 -0400):
>>>>> From: "Kenneth Brody" <kenbrody at bestweb.net>
>>>> [...]
>>>>> > If you have a selection set that can do it for you, then simply use
>>>>> > the selection set in your processing to help the filtering process.
>>>>> >
>>>>> What command am I using to execute a selection set before I get to the
>>>>> browse lookup processing?
>>>>
>>>> In your browse lookup processing:
>>>>
>>>>    If:  not selectionsetname
>>>>  Then:  drop ; end
>>>>  [... any additional processing you need here ...]
>>>>
>>>> --
>>>> KenBrody at BestWeb dot net        spamtrap: 
>>>> <g8ymh8uf001 at sneakemail.com>
>>>> http://www.hvcomputer.com
>>>> http://www.fileProPlus.com
>>>>
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> Filepro-list mailing list
>>> Filepro-list at lists.celestial.com
>>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>
>>
>>
>>
>>
>
>
>