>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,

I do the same thing with views, I don't use SET FILTER especially with grids as the grid's handling of a filtered recordsource completely removes any advantage of optimization.

I stand by John's original SET FILTER being one of the VFP things to avoid.