Summary: | ERROR.TYPE for "Search out of range" in Excel return 7 but in Calc #N/D | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | gmolleda |
Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | buzea.bogdan, erack, himajin100000, oliver.brinzing, xiscofauli |
Priority: | medium | ||
Version: | Inherited From OOo | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 108827 | ||
Attachments: |
error.type example
view error |
Description
gmolleda
2018-11-18 07:21:00 UTC
already reproducible with Version: 5.4.7.2 Build-ID: c838ef25c16710f8838b1faec480ebba495259d0 CPU-Threads: 4; BS: Windows 6.2; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: single Created attachment 146724 [details]
error.type example
https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/interpr1.cxx?r=4ddd6f32#7186 https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/interpr4.cxx?r=32d846dc#1912 https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/interpr1.cxx?r=4ddd6f32#9663 https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/interpr1.cxx?r=4ddd6f32#9674 Also reproduced in Version: 5.2.0.0.alpha0+ Build ID: 54862a932fc9ccc1788e91629818ec6666ec1c09 CPU Threads: 4; OS Version: Linux 4.15; UI Render: default; Locale: ca-ES (ca_ES.UTF-8) @Eike, I thought you might be interested in this issue... Calc has more detailed errors than Excel. In this case the Err:502 (IllegalArgument) is because the field index to VLOOKUP() is 2 but there is only one field. Calc returns #N/A only if the lookup-value is not found in an otherwise correct context. Excel seems to return #N/A in any error case of VLOOKUP(). Actually ERROR.TYPE() returning #N/A can happen with any of the more detailed Calc error values because there is no defined mapping (and can't be), which exists only for the seven error values Excel knows. Mapping Err:502 to #N/A (=7) is not a solution because in other (or most) context it may be #VALUE! (=3) instead, or something else depending on what Excel returns for some function's error (which in most cases #VALUE! isn't helpful at all). This isn't really solvable unless we'd transport additional information with each error what it might be in Excel in the given context just in case there would be an ERROR.TYPE() evaluating it. Which I think would be overdone and I'd rather close this as wontfix. Dear gmolleda, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug Created attachment 155964 [details]
view error
The bug continues in LO 3.3.2
|