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

There are reasons more than I'd list here:
1) Performance, no matter how much it's enhanced still not as performant as other ways.
2) Reliability. With undeterministic expressions + a grid you might end with something that would make you cry "what's happening". Visually it happens and hard to solve.
3) Record pointer movement. Where it's really. You generally think where it should be but be carefull.
4) No good reason to use.

SQL (or views which is basically just another SQL) is one but not my preference. If you can do it, then traditional xBase relations and set key to is the simpliest and fastest. Not always you have a chance that way, then SQL or View might be required.

A simple demo filter expression could be:

set filter to order_date = date()

It sounds to be very innocent, isn't it:) Beware that's an evil.
Cetin