Bug 43154 - EDTING : Empty string "" equivalent to any number with several functions.
Summary: EDTING : Empty string "" equivalent to any number with several functions.
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Master old -3.6
Hardware: x86 (IA32) Windows (All)
: high blocker
Assignee: Kohei Yoshida
URL:
Whiteboard: target:3.5
Keywords: regression
Depends on:
Blocks: mab3.5
  Show dependency treegraph
 
Reported: 2011-11-22 00:01 UTC by GerardF
Modified: 2011-11-22 11:59 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Spreadsheet reproducing the bug (11.39 KB, application/vnd.oasis.opendocument.spreadsheet)
2011-11-22 00:01 UTC, GerardF
Details

Note You need to log in before you can comment on or make changes to this bug.
Description GerardF 2011-11-22 00:01:31 UTC
Created attachment 53761 [details]
Spreadsheet reproducing the bug

LibO-dev 3.5.0 
Build ID: 4f11d0a-adcf6d5-c4bb9bd
on Windows Vista.
master~2011-11-16_23.49.24_LibO-Dev_OOO350m1_Win_x86_install_en-US.exe

With a range containing empty string like result of IF(A1=1;1;"") and A1<>1,
functions SUMIF and COUNTIF counts empty string when criterion is a number.

Same behavior with search function MATCH or VLOOKUP :
If "search criterion" is a number and if this number is not in the range or if empty string is above this number, MATCH returns position of empty string.

See attachment, it will be more clear.
Comment 1 Jean-Baptiste Faure 2011-11-22 03:02:57 UTC
Confirmed under Ubuntu 10.04 x86_64 with my build : LibreOffice 3.5.0 
Build ID: 997ac87-7085c55-8b4f344-a2e750f-ce71330

should be in LibreOffice 3.5 most annoying bugs.

Best regards. JBF
Comment 2 Petr Mladek 2011-11-22 04:42:17 UTC
Kohei, Marcus, could you please have a look?
Comment 3 Kohei Yoshida 2011-11-22 09:52:13 UTC
I'll take a look.
Comment 4 Kohei Yoshida 2011-11-22 10:14:03 UTC
Set it assigned again.
Comment 5 Kohei Yoshida 2011-11-22 11:57:13 UTC
Aha!  It was a simple typo causing this trouble.