Sorry Guys,

maybe I have missed a trick here.
I have an IBOQuery that is connected to a large 2.2 million record database
table.

The largest search a user can do would be a whole area like LONDON for
example (250,000 records).

Now obviously most users do more sensible searches but even still we want
the records displayed in the grid quickly.

I use a DEV Express Quantum Grid that has a LoadAllRecords setting which
allows you to simply use the grid to do the sorting. This is no good so we
use in in PartialLoad mode with 80 records buffered max.

To sort right now, when a user clicks on the column header we close the
query, add 'sort by columnX asc' to the sql for example and open the query
again, we also put the correct sort marker in the grid heading.

So the problem with that is that if a user is on a certain selected record
and then decides to sort the grid then because we close and open the query
we lose the select record.

Are you basically saying that I can use the IBO Query to sort the data
without a) having to open and close the query and b) it wont bring anymore
records to the client than needed? (i.e. 80) and lastly the grid will keep
its selected record? ( I realise that if the record select becomes record no
800 when the grid is sorted then 800 records will have to be brought over).

Basically if there is a better way of doing this guys, Im all ears.

Thanks,

Andy,