Sort/select processing when sorting by associated fields

[Kenneth Brody]

Quoting Jay R. Ashworth (Wed, 30 Jan 2008 16:39:28 -0500):

> On Wed, Jan 30, 2008 at 04:34:16PM -0500, Kenneth Brody wrote:
>> >What I was trying to get at was why that decision was taken in the
>> >first place.  We're assuming, here, a selection *set* (which supersedes
>> >processing, right? -v only runs against the records that survive -s?)
>> >that includes an associated field.  Or perhaps I've had too much to
>> >drink.  Already.  :-)
>>
>> Yes, the sort/select processing only gets records that make it through
>> any selection set.
>>
>> Also, remember that, if the record has all instances of the associated
>> field blank, and blank does not pass the selection set, the record won't
>> be selected.
>
> So this behavior only pertains to sort/sel processing on an associated
> field which does *not* also occur in a selection set used at the same
> time...

No, the rule is whenever you are dealing with associated fields.  filePro
will look at all non-blank instances, unless they are all blank, in which
case, it will look at (only) the first instance.

If you are sorting on an associated field, then it will be passed through
the selection filters for each non-blank instance, or the first instance
(only) if they are all blank.

[...]

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