>>My grid displays the content of a Remote View with 1.000.000+ records from SQL server. I use data fetching to speed up the application. The user can click on the column's headers to change the order of the grid.
>>
>>If I use indexes to quickly change the order, then the whole table is downloaded. This is very slow. So probably I have to make new query every time the user changes to order. The problem is that the SELECT expression is read-only at runtime in the Remote View. I can't use "?parameters" at ORDER BY as with FILTER in the View Designer. I can't use "CREATE VIEW" to overwrite the existing Remote View because more users are using the same application with the same .DBC.
>>
>>Any ideas? Thanks in advance!
>
>I think you simply have to make sure you download only a subset of the data - you must decide, based on the structure of the data, whether this should be by client, by date range, etc. Then, once the user gets a small subset of the data, you can create temporary indices on this subset.

That's why I'm using data fetching to download only 100 record of 1.000.000, but I'm loosing this benefit when indexing. I know that this is against client/server logic, but my customer wants to browse around the whole table and change the order at runtime so I'm looking for a solution to change the order of the view at runtime without loosing the comfort of the data fetching.