Jim,

>>To illistrate where i'm using SET FILTER for, you might look at the northernwind database in access. If you open the clientsform, you're able to filter the table. Just tell me what do you think is the best way to filter the table ? If you find another suitable alternative, please tell me.
>>
>
>Walter,
>
>A view created at runtime.

Jim,

I'm working with the localized version of Office 2000, so I might be wrong about the names.

-Just open the northerwind database in access and open the product form.
-Select the category box and apply a field filter
-Skip forwards, backbards, release the filter and apply two others simutaniously.
-Change the order of the table
-Finally issue the browse function (right mouseclick on the form and the second option), select a row and display the form mode again

How would you implement this with p-views if this table contains about 5,000 records ? IMO, the set filter approach is more simple to apply and gives more performance, particulary when selectivity is low.

I understand you would argue this design, but therefore we argue about the UI and not whether SET FILTER could be usefull.

I use this approach in my aplication framework to provide the same flexibility as these Access applications do. If I could determine if a table would be to large to handle this with filters in particalar circumstance, I might disable the filtering for those field which can not be optimized, or might notify users that the particular filter can cause performance problems.

Walter,

Walter,