Solved: Syntax question: Range(....)

[YellowLabPro]

In the first two lines of code, this is confusing me why the first one is accepted/valid by the compiler rather than the second one.
The third "&" is required to create the proper range stmt. for the compiler, why?

[VBA]
Range("J" & i & ":O" & i).Delete shift:=xlShiftUp
Range("J" & i ":O" & i).Delete shift:=xlShiftUp
[/VBA]

[VBA]
For i = lrwSource To 3 Step -1
If Cells(i, "O").Value = "x" Then
Range("J" & i & ":O" & i).Delete shift:=xlShiftUp
End If
Next i
[/VBA]

[Norie]

Doug

It just is.

Why do you think it wouldn't be needed?

You are concatenating "J" and(&) i and(&) ":O" and(&) i.

[Bob Phillips]

When concatenating, every item has to be acted upon, they don't do it implicitly.

[YellowLabPro]

Thanks Bob.

Norie to answer your ?
When reading it literally- it would be:

[VBA]Range("J3 & : O3").cells.delete[/VBA]

which if this were even possible is saying these two cells,
not the range of

[VBA]
Range("J3:O3").cells.delete
[/VBA]

[Bob Phillips]

[vba]

Range("J3,O3").cells.delete
[/vba]

[Norie]

Thanks Bob.

Norie to answer your ?
When reading it literally- it would be:

[vba]Range("J3 & : O3").cells.delete[/vba]

Eh, no it wouldn't.

For just two cells it would be this.
[vba]
Range("J3, O3").Delete[/vba]

PS You don't need Cells here.

[YellowLabPro]

Bob,
Had not thought about it like that, that is cool. What I was trying to convey was the idea of being literal, the " & : " would not be written / read that way.
But I get what you meant in the first post regarding concatenating and I see your point here of a range being separated by the comma providing two valid ranges....
Thanks.... keeping me on my toes