Bug 74437 - BUSCARV (LOOKUPV) Error and Excel 2003 interoperability
Summary: BUSCARV (LOOKUPV) Error and Excel 2003 interoperability
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.2.0.4 release
Hardware: All Windows (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-03 12:06 UTC by Nicolás
Modified: 2015-09-04 03:01 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
images tha show bug in action (1.57 MB, application/zip)
2014-02-03 12:06 UTC, Nicolás
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolás 2014-02-03 12:06:15 UTC
Created attachment 93279 [details]
images tha show bug in action

Hi, i´m Nik from Argentina. First sorry about my english i speak spanish. 
I Use every days Libreoffice Calc. Before i use 4.1.4.2 version, and everythings Ok. When install 4.2.0.4 i found some Bugs. Two that are important. One in new versión (4.2.0.4) show “N/D” that you can see in image “Libreoffice 4.2.0.4 Bug BUSCARV Function.png”, when find cells in other sheet, the   function is: 

=BUSCARV(B15;'C:\Mis Documentos\COSTOS\[Precios_Actuales.xls]Precios'!$B$4:$AE$400;22;0)

I want find in “Precios_Actuales.xls”, in “Precios” from $B$4:$A$E400  the equal respect cell B15 from origen  (NS0280 Llada.xls in this case), the cost  in row 22 (W).

Excel 2003, Openoffice 4.01 and Libreoffice 4.1.4.2 function works perfectly, but not in Libreoffice 4.2.0.4. (Files: “NS0280 Llada.xls” and “Precios_Actuales.xls”)

Other thing that was intresting that functin support relative path. Ejample: not write   'C:\Mis Documentos\COSTOS\[Precios_Actuales.xls]Precios', just write '.\[Precios_Actuales.xls]Precios', that must work perfectly with pendrives and not, and  Linux  & Windows, etc.

The interoperability respect Excel has change, now  the file “PRECIO TERCEROS 27-01-14.xls” that use a simple porcentual function  show a lots of zeros. Look it in the image “Libreoffice 4.2.0.4 Bug EXCEL.png”..

I see a change in Excel functions work, but i think you can reseolve that quickily with and option in preferentes, where you can select  functions “like” 4.1.4.2 or  4.2.0.4 type.

Thanks a lot  you make a great job. Nicolás.-
Comment 1 Nicolás 2014-02-03 12:09:41 UTC
I use Windows and Linux (Debian testing with Mint LMDE repositories and Sabayon), i can't probe this bug in the Linux version of Libreoffice 4.2.0.4, because it's not in repositories at now (day 02/01/2014).
Comment 2 QA Administrators 2015-07-18 17:43:02 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
Comment 3 Maxim Monastirsky 2015-07-30 12:58:34 UTC
Never confirmed by QA, moving to UNCONFIRMED.
Comment 4 raal 2015-07-30 13:56:24 UTC
Hello Nicolás,
I've opened file PRECIO TERCEROS 27-01-14.xls and I see the values in column "Precio" (not zeros).

Vlokup issue seems to be duplicate of bug 85553 - when I save file as .ods, then I can see the values.

Please, test with actual version of LO and let us know if this bug can be marked as duplicate of bug  85553. Thank you
Comment 5 Buovjaga 2015-08-01 15:20:38 UTC
NEEDINFO, while we wait for Nicolás.
Comment 6 QA Administrators 2015-09-04 03:01:17 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-09-03