Wow,

I didn't know about the Range.Cells. I just figured that the "for each" would loop through the tiniest part of the collection: a cell, which it always did until I recently added the .Column(1) part.

However it seems logical to add the .Cells now that I read it.

Thank you!

Range("A1:G10").Select

' Works correctly:
For Each rngCel In Selection.Columns(1).Cells
Debug.Print rngCel.Address & " as part of " & Selection.Columns(1).Address
Next

' Works correctly:
Set rngSelection = Selection.Columns(1)
For Each rngCel In rngSelection.Cells
Debug.Print rngCel.Address & " as part of " & rngSelection.Address
Next
End Sub
[/code]

I have no explanation for this but at least it works :-)
(remember to loop through areas also when your working with user selection)

For Each rngCel In Selection.Columns(1).Cells
For Each rngCel In rngSelection.Cells

For further assurance, the third should be:

For Each rngCel In rngSelection.Cells

Rows() and Columns() both return the entire row or column (within the range specified). Range() and Areas() return the individual cells by default.

I've developed the habit of always explicitly calling out the level of detail I want. So I would code

For Each rng in Range("A1:G10").Cells

to mean that I want to loop through all cells individually (even though Cells is the default for Range), and

For Each rng in Range("A1:G10").Rows

to mean that I want to loop through the rows.

If you change your first loop to "Selection.Columns(1).Cells", you would force the desired behavior rather than rely on the default for the Columns() range reference.