>>Set filter is greatly enhanced but I still keep it in my "commands not to use list":)
>
>why may i know ? and what is the alternative? SQL joins?
>
>any specific conditions where it leads to errors ?
>
>Thanx
>suhashegde

I am not sure what Çetin's reasons are, but my own reasons would be that SET FILTER, within a grid, can be very slow. Sure, there are cases where I use a filter. But for me, it is not the method of choice, to get a subset of records in a parent-child case, and the reason is performance.

I use a parameterized view, because:

Unlike SET FILTER, it is much faster.

It allows me to create a temporary index, to show data in the order desired by the user (this is indicated by the user, by double-clicking on a grid header). This is not practical with SET FILTER, because all records would have to be indexed. Nor is it practical with SET KEY, because this command already relies on a specific index.

Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)