That's not necessarily true either. If you want to do a search on two fields

LOCATE FOR FIELD1=SOMETHING AND FIELD2=SOMETHING

LOCATE FOR FIELD1=SOMETHING

LOCATE FOR FIELD2=SOMETHING

You'll need three index tags to do what you suggest. The best practice is to use SQL and have the two indexes and not to grab more data than necessary.

>Hi Fred,
>>
>>Not entirely true. As long as the filter matches an index tag, you'd be hard pressed to notice a slow down. If it doesn't match an existing tag, then your statement is VERY true.
>
>If we talk about good practice.. There is nothing to compare:
>
>

>set near on
>seek mykey
>scan rest while mykey = myfieldcode
>endscan
>

>
>SET FILTER will be good enough just: As long as the filter matches an index tag.. To find the EOF() state... huff.. :)
>
>Claudio