Hello,

I have a grid with RowMode and MultiSelect both set to true. This is in Access 2010.

In the video you see that initially the list is sorted by the "Priority" column. I then resort by the "Customer" column and select 4 rows. The button on the right simply tells me how many rows are selected using this simple code:

Dim SelectedRows() As TSelItemInfo
SelectedRows = ProcessingStepList.SelItems.GetArray
MsgBox UBound(SelectedRows)
Erase SelectedRows

At first it correctly reports that 4 rows are selected. I then re-sort the list by clicking the Priority column header. The list "appears" to still have 4 rows selected but the button says that only 1 row is selected.

I tested this many times and sometimes it reports fewer rows than it shows and other times it reports more rows. It is very random.

While waiting for a reply, I decided to create a workaround but am running into even more problems.

The ClearSelection method is not working. If I select several rows, resort the list interactively by clicking on the column headers, and then call the ClearSelection method: some of the rows are NOT deselected.

What version of iGrid are you using? Is it the latest build 6.0.20?

If not, then upgrade your iGrid OCX to the latest version and try to reproduce the problem in it. The latest build fixes some selection issues, and this may be related to your situation too.

If the latest build does not fix your problems, prepare a demonstration sample and send it to us for further consideration.

I was using version 6.0.0 but I upgraded to version 6.0.20 and the problem persists.

After a lot of testing, I know what is causing the problem! It happens when the first column is not visible (bVisible:=False).

The attached demo clearly shows the problem.

  iGrid Problem.zip (68kb) downloaded 102 time(s).

Select two or more rows and then resort the list by any column and you will see that the count of selected rows is zero but the list still shows the same rows selected. Then go and make the first column visible and the problem goes away.

Edit: There is no reason why I need to place a hidden column in position 1 so this problem has a very easy solution.

Our policy is to have robust and totally bug-free components, so I will definitely look at the problem. If the problem on our side, I will fix it and include the fix in the next public update of iGrid.

Thank you.

I investigated this issue. Yes, it was a problem on our side. It was caused by the latest improvements in the algorithms related to selection.

I have fixed the iGrid OCX and sent you the link to the fixed version to your email for checking.

I tested the new version and the problem is fixed. Thank you for taking care of this so quickly!