Hi Hilmar,

I wanted to try using view after reading your reply, but it seems VFP only create views for database(.dbc) but not for a table(.dbf).. but for some reason I have to use .dbf file, so is it impossible for me to use view in this case?

Jimi

>You already said what was the disadvantage: it is slow. This seems to be some sort of bug with VFP: Rushmore Optimization doesn't seem to be used with grids/filters.
>
>The correct thing to do is to use a view. A view is like a query, but updatable (changes made to the cursor can be written back to the original tables).
>
>Hilmar.
>
>>Thanks Cetin,
>>
>>Just wanna know more, what is the disadvantage of using grid with filters?
>>
>>Thanks,
>>Jimi
>>
>>
>>>>hi,
>>>>
>>>>Showing data with a grid and set filters to view the wanted records is a very common thing.. i think most people should have tried it..
>>>>
>>>>I also have a form to do such thing, but for one of the filter settings, the grid would become VERY slow, each click on the grid takes 3-5 seconds to get focus, but it works just fine with other filters..
>>>>
>>>>would anyone please have a look and see if the following filter would make the grid act so strangely slow?
>>>>

>>>>select MyTable
>>>>
>>>>filter_expr=allt(thisform.myTextbox.value)  && see what the user want to see
>>>>filter_desc=iif(UsingFirstLang(), "name1", "name2")  && check different field when using different language setting
>>>>set filter to at(filter_expr, &filter_desc)>0
>>>>
>>>>thisform.grdIT03Itemlist.refresh()
>>>>

>>>>
>>>>any idea? Please help~
>>>>Jimi
>>>
>>>Jimmy,
>>>Filters and grids are not common :) Whenever possible do not use (personal opinion).
>>>Instead try making Recordsource directly an SQL (needs index on name1 and name2). Then all you would do is a grid.refresh or grid.recordsource=grid.recordsource if not indexed (I don't know why but grid goes blank if not indexed).
>>>Cetin