GNOME Bugzilla – Bug 80126
vlookup range can't contain twice or more rows than what actually contains data
Last modified: 2004-12-22 21:47:04 UTC
vlookup() function returns 0 if you have range that contains twice as much
row as the range containing data. (One needs to define a larger range for
aditiona data rows being added in time without the need to alter the
Best way to describe this problem is by looking at the attached sheet. The
D12 cell contains a function =vlookup(4;A1:B24;2). This is the last range
when it works correctly on data in A1:B12 (returning D). Change the
expression to =vlookup(4;A1:B25;2) and it will return 0 instead of 'D'.
Created attachment 8003 [details]
example sheet using the vlookup function (created in 1.0.4)
THis is only a problem for @approcimate == TRUE (the default if
@approximate is not given.)
Fixed in cvs-head. The fix consists essentially of replacing
value_area_fetch_x_y with value_area_get_x_y in find_index_bisection
and removing a check for NULL.
Perhaps we should back-port this?
Sounds like a good candidate for back porting.