Row Selection By Check Box

 

 

  I want to select Rows using Selection Box.

 

  Is there any Inbuilt check box for each Rows for Selection or do we need to loop through all rows with adding a check box Column?

 

 

 

In future Release if they have option like this will be easier..!

So that you can loop through Selected Rows.

 

 

If you add a column you have to loop through All Rows for checked status...

It's time consuming...!

 

 

 

 

 

What is difference between looping rows and selected rows? The only thing that would be different when you would have "Rowselectioncheckbox" you don't have to set .HasCheckbox for a ReportItem. You still have to check 'selected value' and todo this, you have to loop rows. Maybe I don't understand what you are trying to say and I would like to hear what you are trying to accomplish.

 

   

 

Suppose I have 1000 and above records, I need to select some records ( Ex: 10 to 15 Records) and do some action...

 

 

               If there is a Row Selection Check box I can simply use this Code

 

                       for i=0 to ReportControl1.SelectedRows.count - 1

                               ' Do any Action

                               ' This will loop only 10 to 15 Records....!

                        next

 

 

               then you have to loop through all rows to check whthere row Selected or Not...?

 

                    for i=0 to ReportControl1.Rows.count - 1

                         if ReportControl1.Rows(i).record.Item(0).Checked=true then

                               ' Do any Action

                          end if  

                               ' This will loop 1000 and above Records....!

                        next

 

 

In my case I have records sometime above 10,000.

 

So that is the reason i am expecting some option like

 

 

 

 

 

 

  

 

 

 

                

 

 

 

Hi,

 

If you are talking about few thousand records, I wouldn't worry about iterating "those few records". If it would take more than a second to iterate entire collection, I would consider what Hemish proposed. Well, you need some 500.000 records (tested with my own laptop) to get to that second "waiting" and users don't notice that small delay (in your case).