>>Rebecca,
>>
>>Yes, I imagine you'd have to reindex it after each Requery(). The Requery() is basically giving you a new table each time.. I'd use a custom form method to handle the Requery() and indexing, and call it from Init() and wherever else you need.
>>
>>>I tried setting indexes in the load of the form that uses the grid (because I could find nothing in the view definition that indicated an index--only a sort order). However, I have a requery in the refresh of the form because the user can add records. The requery lost the indexes as near as I can tell. Do I need to recreate them every time I do a requery????
>>>
>>>Thanks a lot for your help, this one has me stumped!
>
>Hi
>I finally gave up on the indexing and just created two views, each one sorted separately, then when they click the radio button to change order, I requery the new one and switch to it. It works fine. Never did figure out why indexing wouldn't work. Oh, well.
>Thanks a lot.
>Becky
Rebecca,
I do the similar. Index the view on form.init and use requery("view") freely. Grid header class has code to change tag to its related order on click. All works well. AFAIK once you create an index for a view it's updated automatically until you close it. OTOH I don't have an idea why you might be losing it.
Cetin