It works  backwards because then the rows  stay where you are until you have
processed them. Otherwise you have to move down if you don't delete a row  and
stay still if you do delete. = more complicated looping.

The commented-out part of your code is setting a variable with a range  of
rows that represent what you want to work  through.

The later part of your code works  with "Selection".

You have never actually selected  the area you found, so it's working with
whatever selection  you had when you entered the code.

Instead of Selection, use rngToSearch, and it'll probably work. Or do a
select of rngToSearch.

The reason it works backwards is that if you worked forwards you would have
to compensate for the situation of two consecutive blank rows. I.e. (say
they're 10 and 11)

i = 10 (set by your For statement)
row (i) is blank, delete it, row  11 moves to row 10
"Next i" - i is now 11
row(i) is not blank (remember it was row 12 originally)
etc

Working backwards eliminates this problem. I.e. delete row 11. Row 10
stays where it is. "Next i" now moves to 10.

Thank you. It seems like that backward concept is
important.

Yes indeed. Order of processing is important whenever items are being
inserted or deleted. It's not usually so important at other times.

For a situation like yours, it is certainly possible to do the work  in the
forward direction, but the code would be approximately twice as complex: an
inner loop would be required, and the moving last row  would need to be
accounted for.