>OK views make sense for single tables in cases when I cannot find a simple set key version:)
>Cetin
I think you can ALWAYS create an index for a SET KEY TO. The problem is in the sorting. You need different indices for different sort orders (I am thinking about indices with a concatenated expression - the first part would be used to replace a filter; the remainder would control the viewing order). I don't think this would be efficient or practical:
The framework I use creates indices "on-the-fly" when a user double-clicks on a column header. It will even sort on multiple columns (for this, the user Ctrl-clicks on the second, third, etc. column). This definitely requires temporary indices. All this works much faster on a view. As an example, the subset of 100 records I am looking at are indexed quickly with a view. With a filter - or SET KEY - all 60,000 records would have to be indexed.
Hilmar.
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)
