Issue 117790 - Inconsistency between OOo and EXCEL - INT function
Summary: Inconsistency between OOo and EXCEL - INT function
Alias: None
Product: Calc
Classification: Application
Component: open-import (show other issues)
Version: version58
Hardware: PC Windows XP
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2011-04-09 22:33 UTC by carlc451
Modified: 2013-08-07 15:13 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description carlc451 2011-04-09 22:33:22 UTC
* Per OOo documentation, INT only operates on numbers. Text-that-looks-like-numbers returns a value of '0'.
* EXCEL happily takes a text field that looks like a number, and processes it as a number.
--- I just imported a long-used business spreadsheet that parses its 'Job Numbers' field for the imbedded job-priority.  [=RIGHT(jobno,1)]
--- That priority is then used as the index value for an HLOOKUP of Labor and Travel pay rates.
--- Until I spotted the HUGE DIFFERENCE, EVERYONE was getting paid PRIORITY-0 (Emergency)rates, :-)
--- Easy fix (once I figured out what wasn't working the same) - global substitution of "VALUE" for "INT" --- and all the bonuses were taken back :-(.
--- I'm glad this inconsistency generated such a huge, and obvious change in computed pay values.  I spotted almost immediately.  If this had come up in a more obscure section, the consequences could have been horrific.
Comment 1 Oliver-Rainer Wittmann 2012-06-13 12:26:27 UTC
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.
Comment 2 Edwin Sharp 2013-07-21 09:00:31 UTC
INT gives #VALUE! when processing number in cell formatted as text.

Excel 2007 works the same whether cell format is number or text.

Rev. 1503704 Win 7