VLOOKUP define table array with just columns

Sorry if this is just too obvious but I have always defined a Vlookup table_array using row and column coordinates. I was looking at a Vlookup formula in colleagues workbook and it defined only columns.

So instead of what I would normally consider using:
=VLOOKUP(A2,'sheet2'!$A$2:$G$100,2,FALSE)

they had simply defined the columns:
=VLOOKUP(A2,'sheet2'!A:G,2,FALSE)

I couldn't find any reference to using Vlookup like this so I wondered if this is something others use, or whether there could be issues doing it this way. Obviously this is an easier way to enter particularly on larger datasets where you can simply drag the columns to define the table array.

yes, you can use that way - but it will address 1,048,576 rows - depending on version of excel

better to use a range
if you want to future proof - say your range is $A$2:$G$100 but it grows
then use
$A$2:$G$100000

would be better than A:G

IMO using entire columns has more drawbacks than advantages. One of the former is that you will be unable to use those columns for anything else. Your sheet might get bloated, etc.. ( because, once one uses entire columns, one tends to use it in all formulas where applicable..)
OTOH as XL has the Excel Tables feature why not use this technique for ranges that might change?

IMHO... No issues here, but.

1. Some functions work FINE with whole columns (COUNTIF(s), SUMIF(s), VLOOKUP, INDEX-MATCH, etc).

2. Other's don't (SUMPRODUCT) which will calculate EVERY row.

3. NEVER use whole columns with array formulae

4. The only issue is that VLOOKUP returns the first matching result it sees.... so if your layout is poor... and a match for A2 occurs ABOVE the desired result... th eone above is the one you'll get.

5. I tend to use whole columns where it's OK to do so.

Others will, no doubt, chip in as well.

And they have... and don't agree!

https://fastexcel.wordpress.com/2015...a-or-bad-idea/