Home |
Search |
Today's Posts |
#10
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Bob Phillips wrote:
But ranges are not a collection, so you are trying to make something look like something else. Are you suggesting that Range("my_range") is not a collection of cells? Where is the specification that makes that clear? Precisely how does it differ from a collection of cells? I'm not trying to make Range("my_range") look like anything but exactly what it is. A close relationship does not make them the same. Far better to follow the object model in my book. How does Range("my_range").Item(1) deviate from the object model? That's all that Range("my_range")(1) is, just as Worksheets(1) is the shorthand for Worksheets.Item(1). And what is the big deal on a few keystrokes. Most commands can be auto-completed, so a few keystrokes in the grand scheme of writing a serious app is irrelevant, it is not a race. It's not a big deal; it's a small advantage just like the increased speed of execution is. But it's a bit baffling to me that a serious programmer would bypass those features without being able, apparently, to articulate a single advantage for the more cumbersome form. Alan Beban |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
inserting a named range into new cells based on a named cell | Excel Discussion (Misc queries) | |||
Named Ranges - accessing a cell | Excel Discussion (Misc queries) | |||
If any cell in named range = 8 then shade named range | Excel Programming | |||
Accessing named ranges in Excel from VBA | Excel Discussion (Misc queries) | |||
Accessing Named Ranges | Excel Programming |