ExcelChampion
Well-known Member
- Joined
- Aug 12, 2005
- Messages
- 976
Going back a couple of posts regarding named ranges and INDEX/MATCH, I personally like to throw the INDIRECT function in there as well...
=INDEX(INDIRECT("Data!$F:$F"),2):INDEX(INDIRECT("Data!$F:$F"),lRow)
(where lRow is MATCH(9.99999999999999E+307,'Data'!$I:$I)
Now before you all start jumping on me telling me INDIRECT is volatile, let me explain why I do this...better yet, set up your own example with data in column F and use the formula above with out the INDIRECT function, and then delete column F...You will get the REF error in your named range...something you won't get with INDIRECT.
And it works with rows, too. Something very common that happens is when an end user wants to start a data set over (say for a new year) with new data, instead of just clearing the rows' contents, he deletes the rows...resulting in the REF error.
=INDEX(INDIRECT("Data!$F:$F"),2):INDEX(INDIRECT("Data!$F:$F"),lRow)
(where lRow is MATCH(9.99999999999999E+307,'Data'!$I:$I)
Now before you all start jumping on me telling me INDIRECT is volatile, let me explain why I do this...better yet, set up your own example with data in column F and use the formula above with out the INDIRECT function, and then delete column F...You will get the REF error in your named range...something you won't get with INDIRECT.
And it works with rows, too. Something very common that happens is when an end user wants to start a data set over (say for a new year) with new data, instead of just clearing the rows' contents, he deletes the rows...resulting in the REF error.