Bug 33426

Summary: Lookup function Err:504 when search/result vectors are from separate file
Product: LibreOffice Reporter: Bill Kirby <wjkirby>
Component: CalcAssignee: Kohei Yoshida <kohei>
Status: RESOLVED FIXED    
Severity: normal CC: scott.benninghoff
Priority: medium    
Version: 3.3.0 RC4   
Hardware: x86-64 (AMD64)   
OS: All   
Whiteboard: target:3.4
Crash report or crash signature: Regression By:
Attachments: Zip file containing spreadsheet samples and screenshot image

Description Bill Kirby 2011-01-24 12:41:51 UTC
Created attachment 42404 [details]
Zip file containing spreadsheet samples and screenshot image

This problem occurs on both my Ubuntu Linux (64 bit) and in Windows XP SP3.

When trying to use a separate file that contains the search and result vectors the function fails with an Err:504. If I place my search/result sheet within the same workbook and try the Lookup formula again, it will work. This function worked fine in OpenOffice. Sometimes I may get a Err:511. I usually save my files in .xls format but tried .ods format and got the same results.

I've attached sample sheets of what I'm working with. My criterion is from B column in main.xls and my search is from B column in search-result.xls and result is C column of search-result.xls. I've also added a screenshot of the Lookup dialog window showing the error.
Comment 1 GerardF 2011-01-27 08:08:13 UTC
*** Bug 33588 has been marked as a duplicate of this bug. ***
Comment 2 Kohei Yoshida 2011-03-03 14:39:05 UTC
Indeed, LOOKUP, HLOOKUP and VLOOKUP all had to be adjusted in order for them to handle external references correctly.

Hopefully this is fixed for good.
Comment 3 Luis Thiago 2011-03-16 10:20:21 UTC
This error still has been occurring with this functions and other functions (IF, SUMIF, COUNTIF...) in external references. And all functions created by "Function Wizard" gives error, the external references aren't inserted on the function.

LibreOffice 3.3.1 
OOO330m19 (Build:8)
tag libreoffice-3.3.1.2
Comment 4 Kohei Yoshida 2011-03-16 10:31:49 UTC
It's fixed in 3.4.  Look at the target info.