>>>>>I was trying to search a view and got an error because the search class I was using couldn't find an 'order'. It was assuming that I had done a SET ORDER TO on a table. That made me realize the view itself didn't have an order, just the underlying tables. I was sort of assuming I could search the view based on the TAGS of those table(s), but since the tables are in different work areas that doesn't seem likely. Is that correct, and do I actually have to create a temporary INDEX ON 'blah' so I can do a search in the view.
>>>>>
>>>>>Or am I overlooking an easier way to accomplish the same thing?
>>>>>
>>>>>Thanks in advance for the help.
>>>>>
>>>>>Sylvia
>>>>
>>>>You can apply INDEX ON ... command and create temporary tag(s) for view (buffering property should be set to 3).
>>>
>>>Thanks Edward -
>>>
>>>Can you also tell me whether this is efficient - i.e. is it relatively fast to create these kind of indexes each time (I usually think of indexing as a rather slow process) I want to search through my view? I'm asking because I didn't know if my approach on this needed to be revised?
>>>
>>>Sylvia
>>
>>It depends how many records you want to retrieve. You could apply LOCATE too, but then search will slow down. Actually, SEEK will save some time during the actual search, and LOCATE will save some time when you requery the view. However, indexing is necessary if you want to show view data in sortable grid.
>
>Thanks again,
>
>I forgot to ask you last time why you recommend Buffering with option 3? I typically use 5; is there an advantage in this case to 3?
>
>Sylvia

INDEX command applicable for view only in a case of Buffering=3. Another setting will generate error message. However, you can reset buffering on fly using CursorSetProp().