Link to home
Start Free TrialLog in
Avatar of MIKEV
MIKEV

asked on

Grid logic problem

I can't think today.  I have a grid loaded with items.  I have a loop that runs through each row and selectively removes what rows aren't required.  Here's what I've been playing with:

For x = 0 To Grid1.Rows - 1
   If Grid1.Cell(flexcpText, x, 8) = "0" Then
       Grid1.RemoveItem x
       ' x = x + 1
   End If
Next x

This uses a VSFlexgrid but a grid's a grid for these purposes.  Anyways, my problem is, I've started the loop from 0 to rows-1.  Lets say there's 6 rows when the loop starts.  When I remove an item, Grid1.Rows is now 5, and when x reaches its upper value (6) it's an invalid cell reference beacuse the number of items was reduced.  After the Removeitem, I've tried adding 'x=x+1' to force it out of the loop but for some reason I still get the same problem; 5 items (0-4)  but an x value of 5 because one was removed.

Is there some way of re-assigning the upper bounds of the for loop while the loop is running?  (or some other solution...)

Thanks!
ASKER CERTIFIED SOLUTION
Avatar of Shauli
Shauli

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of LunaSkye
LunaSkye

I have had this problem in the past,

I have not found a way to get past this limitation, once a loop starts, its set..

I have implemented several methods to get past this..
1. When an item is removed, use a goto to move back to ONE LINE before the loop starts so that the loop is re calculated on the fly.

StartAgain:
  For x = 0 to Grid.Rows-1
     If <OkToRemoveItem> = True then
        Grid.RemoveItem x
        Goto StartAgain
     End If
  Next x

The problem with this is that it could present a slowdown, if you have a VERY long list, and the same members are being scanned several times..

The other way is:
2. For the times when you have to remove a list item, subtract one from the loop counter.  So that when it reaches the "NEXT" statement, the counter is incremented up to the next item, which would be the same item you just removed, but now it is a new one.

At the end of the loop, before the item is incremented, place a check.  If the counter is goign past its bounds, exit for.
 
  For x = 0 to Grid.Rows-1
     If <OkToRemoveItem> = True then
        Grid.RemoveItem x
        x = x -1
     End If

     if (x + 1) > Grid.Rows then exit for
  Next x

Maybe this will help

-Andrew
Avatar of MIKEV

ASKER

Awesome, thanks. :)
You are welcome :)

S