Hi Geoff

The documentation doesn't say, and nor does the Hackers' Guide, though it describes it as an alternative to filters.

The Hackers' Guide notes imply that it doesn't work with grids, if I read it correctly, but I have found that in the last week that it works very well indeed. Where forms with a grid were taking up to a minute to fully activate, with tables on a network, they now do so in a couple of seconds.

The good news is that filters appear to work. At first I thought not, since the forms on which I tried it didn't seem to activate. That I think was a framework issue. In the forms' Init I set the key and then the filter, and requeried - and it worked well.

The 'limitation' is that the key must correspond to the order set for the table, but I don't think that bothers me. I only became aware of this feature a week ago, but I am looking to use it in a lot of places across my app.

While the concensus seems to be that views are the way to go with grids, this seems to have more potential. It doesn't use Rushmore, so it scans the order index and delivers faster, at least for the grid.

HTH. Probably be able to tell you more in a week.

Geoff


>Yes but if I have a key range set and a filter set using fields not in the key are both applied