Hi Nadya

No solution is perfect. You may want to look at SET KEY as an alternative to SET FILTER for the places where your application is slowest. Views have a problem too. If the user demands all records from a large table, they will have a long wait. Of course, the trick is to prevent the users ever getting all records <g>.


>>Hi Nadya,
>>
>>So you're saying that they always use SET FILTER on a table rather than a parameterized view? Ouch....
>>
>>I think you made some good points in your letter. Why not take a huge table and do some benchmarks between SET FILTER and a view?
>>
>
>It's a good idea, I will run some tests to prove my point. Our framework is table-oriented, it has FILTER method, which sets filter and also in Init of the form there is SET FILTER command. My idea would be to add new form's property like ViewUsed and update these two places accordingly, so it would behave the same way as before if this property is set to .f., but will have new functionality otherwise...