I was actually ignorant on the columns being defined this way.
Is it possible that with such a huge range, calculation has never been
completed?
Just grasping to understand.
Thanks
scott
>Tyro explained that the original range included all the cells in the worksheet,
>but I agree with your point.
[quoted text clipped - 17 lines]
>> >=VLOOKUP(E7,'C:\Documents and Settings\daryl\Desktop\Cust Maint\
>> >[Vendors.xlsx]Vendor List (2)'!$1:$1048576,3,FALSE)
Tyro - 22 Feb 2008 23:26 GMT
$1:$1048576 involves 1,048,576 rows * 16,384 columns = 17,179,869,184
cells. Do you really need that number of rows and columns in the data for
your lookup array? Could you get by with, say 1,000 rows and 10 columns? Or
do you really over 17 billion cells involved in your lookup array?
Tyro
>I was actually ignorant on the columns being defined this way.
> Is it possible that with such a huge range, calculation has never been
[quoted text clipped - 26 lines]
>>> >=VLOOKUP(E7,'C:\Documents and Settings\daryl\Desktop\Cust Maint\
>>> >[Vendors.xlsx]Vendor List (2)'!$1:$1048576,3,FALSE)
Tyro - 22 Feb 2008 23:50 GMT
In Excel 2007 A:A defines column A which defines all column A entries in all
rows of column A, that is: 1,048,576 rows * 1 column = 1,048,576 cells. 1:1
defines row 1 which defines all row 1 entries for all of the columns in row
1, that is 1 row * 16,384 columns = 16,384 cells
Tyro
>I was actually ignorant on the columns being defined this way.
> Is it possible that with such a huge range, calculation has never been
[quoted text clipped - 26 lines]
>>> >=VLOOKUP(E7,'C:\Documents and Settings\daryl\Desktop\Cust Maint\
>>> >[Vendors.xlsx]Vendor List (2)'!$1:$1048576,3,FALSE)
Dave Peterson - 23 Feb 2008 01:07 GMT
Lots of excel's functions limit themselves to the used range. So I wouldn't be
surprised if there wasn't much of a calculation hit in most cases.
But I bet you've seen excel not reset its used range after you type something
way past the "normal" used range and then deleted/cleared the cell.
I think I'd be more worried about how often the function wants to recalculate.
If I limit my lookup range to A:G (say) and make changes in H:(lastcolumn), then
it won't recalc.
Any change in that lookup range is going to make the function (all the
functions!) that use that range recalculate.
I guess that could be a reason to use =index(match()) instead of =vlookup().
This only depends on a couple of columns:
=index(sheet2!z:z,match(a1,sheet2!a:a,0))
instead of using 26 columns:
=vlookup(a1,sheet2!a:z,26,false)
> I was actually ignorant on the columns being defined this way.
> Is it possible that with such a huge range, calculation has never been
[quoted text clipped - 24 lines]
> >> >=VLOOKUP(E7,'C:\Documents and Settings\daryl\Desktop\Cust Maint\
> >> >[Vendors.xlsx]Vendor List (2)'!$1:$1048576,3,FALSE)

Signature
Dave Peterson