>>>>>>>How would you do the same for a "where" clause?
>>>>>>
>>>>>>SET FILTER doesn't have 'where' clause.
>>>>>
>>>>>ok... Question - there are two ways to filter out records.
>>>>>
>>>>>1. select...into cursor, then use that cursor for you filter.
>>>>>2. set filter on some records.
>>>>>
>>>>>I am picking the first way for now..my "where" clause is a string
>>>>>I built from a user's "search criteria" off of a form. Now I want to fire off the select and get my new cursor with the records I want to display.
>>>>>My questions is:
>>>>>Will the "where" clause search for upper and/or lower case if I only specify in my "where" clause, the field content, which could be upper or lower? If so, how? If I am wrong about "1 and 2" let me know...
>>>>
>>>>Where clause could be the same: UPPER(last_name)="SMITH", but remember to have index tag on UPPER(last_name), else your SELECT is not optimizable.
>>>
>>>
>>>Not sure what you mean by (else your SELECT is not optimizable)?? and
>>>Do you use an index tag when using the SELECT SQL?
>>
>>Not me. Foxpro will use this tag internally.
>
>Does the SELECT work better if you have a index?

Yes, Otherwise VFP will create temporary index (by WHERE clause) behind the scene and it will increase query time.