Thanks Peter, that sounds like it will work for what I'm doing. A couple followup questions -- is the logic here that you can index a view as long as it's not set to table buffering? Why is that? What is the major difference between table and row buffering when issuing TableUpdate() on views? Thanks again, Renoir

>This works for me, but it may not cover all your needs.
>
>First issue a TABLEUPDATE() to make sure you've got no uncommitted records in the view, then
>

>llResult=CURSORSETPROP("Buffering",3,"MyView")     && Row buffer
>INDEX ON Whatever TAG MyTag ADDITIVE
>INDEX ON SomeOtherField(s) TAG MyTag2 ADDITIVE
>SET ORDER TO MyTag
>llResult=CURSORSETPROP("Buffering",5,"DetailView") && Table buffer
>

>
>>I have a need for the view in a grid to display in different orders depending on the search criteria that has been selected. I'm under the impression after reviewing past threads that there is not a way to do this through the project interface, but may be possible progmatically. I keep getting the message that I'm not allowed to create indexes on views for buffered tables. I've considered using multiple views (only the order being different) for the grid source, but that would ineffiecient for a number of reasons that I can see. What is the correct way to handle this? Thanks!
>>
>>Regards, Renoir