I use a report control in multi selection mode. Selecting a few rows - OK. Then I change sort order by clicking the appropriate column header. This operation destroys my selection but the last row.

 

The same if I change the sort order programmatically.

 

Is this a feature or a bug. In my opinion selection should be retained also the sort order was changed.

 

Thanks

 

Using: V12, VB6/SP6 under Win2000 and Vista

 

After repopulating most references will be lost

 

Expanded rows

Selected rows

 

maybe there are more....

 

Before calling Populate store the selected rows (use record index and not row index, they will be different after populating) in an array and after Populate loop the array and select the rows again.

 

 

 

Many thanks. This should work. But it would be much more elegant and speedier if the control keeps this properties by itself...

 

When the control would hold the references of the selected rows it would be easier, thats correct. But how would the reportcontrol "know" to delete all references? As I was typing this I wondered why not.

 

Please look at the SelectedRows class. You can add a selected row to the collection and DeleteAll if you want to.

 

And then again it's the same class  

 

 

sorry for the false alarm