Apache OpenOffice (AOO) Bugzilla – Issue 8088
VLOOKUP and 0 value
Last modified: 2015-03-10 14:27:04 UTC
Hello, in Excel, VLOOKUPing a 0 value will match an empty cell put before a 1; in Calc it does not (gives a #N/A). This also happens when VLOOKUPing an empty cell.
Giuseppe, thank you for using and supporting OOo. Could you please step by step instructions on how to reproduce this error. In Excel on my test box, I cannot look up blank cells.
I did a little testings, and it seems to happen only when using Lotus 1-2-3 compatibility: if Tools -> Options -> Transition -> Transition Formula Evaluation is *checked*, empty cells will be looked up in Excel. Otherwise, they will give a #N/A.
To be honest, I don't know if looking up blank cells is a great feature. I'll let the developers decide.
It could probably be implemented either with an option (VLOOKUP considers blank cell to have value 0) or with an extra parameter: VLOOKUP currently has two obligatory parameter and one optional boolean parameter; we could add one more optional boolean parameter, defaulting to "FALSE", which when changed to true reads blank cells as 0s. Or we could have both this per-formula option *and* a global option setting the default.
Hi Falko, 1 4 u Frank
Set target (based on PCD relevance)
Hi, This is a quite annoying bug(?) when doing a mass migration from XLS to calc as a lot of formulas are broken showing Err:502 XLS sheets (Excell XP) interprets blank cells and the result is 0 Calc gives an empty cell as result So when LOOKUP is used in function calculations, the entire consistency of the spreadsheet is broken Could you change the target to correct this asap A lot of big migrations are starting and this behavior of import filter is a major drawback Thanks Laurent
I also would desperately would like to see this fixed (asap)! If it was not for the vlookup incompatibility (between Office 2k and 1.1.3) of values on blank string values (and the difference of sheetname end-markers ! vs .) my conversion would have been perfect.
FT: I'm leaving so I will re-assign this issue to requirement default user
*** Issue 72781 has been marked as a duplicate of this issue. ***