Q: Vlookup gives unexpected/erroneous results
HI Guys
I used to think I had this spreadsheet thing down pat but I find myself up after midnight wrestling with a VLookup problem! I'm really hoping you can point me to the error of my ways..
I Am a convert from Excel so I may be caught in a mind control thing. I have built a fairly large spreadsheet to do lots of hobby related stuff. I give it away to people who do the same sort of thing as I do. It calculates stuff for soap making but I have just discovered that it gets some stuff wrong - which is potentially dangerous.
I have a simplified version of what of what is happening in the image above. In the cell F2 I have: VLOOKUP(E2,Lookup Values:Results,2,close-match).
Now, I would expect Numbers to look down column B to find the value in cell E2 (1.90) then deliver the corresponding value from column C (19.0). However, it doesn't do this. Instead it delivers the value from the cell above as if it couldn't find a match.
I have tried every setting I can think of to no avail. I have set every cell on the table above to a number with 2 decimal places. I even changed exact match and close match but that just made things worse.
I know it is going to be something that will cause me to kick myself but I need to fix it so no-one gets hurt. Any and all help gratefully received.
Cheers, Grant
PS I think I should mention that I'm doing this on an iPad Air 2 which is a bit new to me. And I just noticed that I am posting in Numbers for Mac. I'm sorry for that but I believe the versions are supposed to have the same capabilities?
iPad Air, Other OS, Latest iOS & Numbers app.
Posted on May 28, 2016 8:42 AM
Hi Grant,
I am sorry to say that I can duplicate your results.
I used the Numbers approach and separated the lookup table. I created it by hand entering the first two numbers in a column and dragging down. With my in/out table I did the same in A and then dragged the formula down in B. I changed it to look for an exact match. Things looked fine until I changed A3 to 1.8 then I get an error. I revised the formula in A2= INDEX(lookup::B,MATCH(A2,lookup::A,0)) which will do the same thing as VLOOKUP(). And it does- it throws an error.
If I retype "2.1" or "1.8" into the lookup table the error goes away and things behave as they ought.
I think this is a genuine bug built in to the way that Numbers fills number sequences. I suggest a bug report to Apple.
quinn
Posted on May 28, 2016 7:30 PM









