>>Hi All
>>How can i achieve the same results as the set filter command, in a grid, without having to set the filter property of the table in the dataenvironment?
>>The problem is when using this method agains big tables, it takes for the form a long time to load.
>>I woul like, instead, to perform a seek, and then display in the grid only records that respond to a certain criteria ( i.e the filter condition ).
>
>To achieve speed, your filter expression needs to have appropriate index tags in the table(s) involved so that it is Rushmore optimizable as much as possible. SET FILTER will use such tags if available.
>
>Another conventional answer is to use a paramaterized view instead. However, this will not be fast either unless the appropriate index tags are available.
>
>How large are the tables and what speed are you seeing? Do you have code samples?

The table has now around 300,000 records, and is indexed by dtos(date). I tried setting the filter expression ( by date, btw ) in the data environment, but there is a delay of around 10 seconds ( in a Pentium 800 in local mode ). My clients are used to immediate responses ( 10 years of Fox :-)))) ), and also they cannot wait all the time, since they give real time support by phone.
Anyway, i found a workaround:
i have two tables now ( for that specific matter ) in the data environment. There is a relation ( by dtos(date) ) into the big table. Setting the date in the first table executes an immediate seek in the second, and then, i just have to refresh the grid, and voila...