Jim,

>SET FILTER whether optimized or not , is slower than no SET FILTER. Speed is a relative consideration not an absolute.

Yep it is, BUT (you knew there was a but), When you do allow users to filter (large) tables, where you cannot live with SQL-views. SET FILTER is a handy tool. When optimized, it's far faster than using views. You might use SET KEY, to filter the table, but I want to allow users to define their own filter.

For example I've got a persons inputform, which users can filter either on, name, adress, city, gender, age, etc.. or any combination of those. It's true that this *CAN* be slow, but that's the problem of the users, He/she either get's it slow or not at all. The form is primarely used for maintaining data, but they can also pick out a user from a grid. This grid CAN be filtered. This way, there is definitely a place for filters.

Walter,