Bug 53134 - Issue with the fonction \months in Calc
Summary: Issue with the fonction \months in Calc
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: x86-64 (AMD64) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-05 01:40 UTC by Michael
Modified: 2013-02-26 01:20 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
a screenshot of the cell of the function when I open the sheet (6.47 KB, image/png)
2012-08-05 01:44 UTC, Michael
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael 2012-08-05 01:40:07 UTC

    
Comment 1 Michael 2012-08-05 01:44:35 UTC
Created attachment 65134 [details]
a screenshot of the cell of the function when I open the sheet
Comment 2 Michael 2012-08-05 01:48:04 UTC
This got submit too early, sorry.

I use the function \months to calculate the number of months between then a date and the current month. The function give me a good answer but when I save, quit and reload the sheet, I get a #name! error on the square and I need to modify the function to get a result. Not a big deal for me since it's a personal sheet but still a bug I wanted the report.
Comment 3 Julien Nabet 2012-08-05 15:21:20 UTC
On pc Debian x86-64, with 3.5 branch updated today, I didn't reproduce the problem.

Could you give a try to the last LO version 3.5.5 and tell us if you still reproduce this problem ?
Comment 4 GerardF 2012-08-06 07:10:31 UTC
Did you save in .xls ?

MONTHS function is not defined in Excel (at least in old versions, 2003 and <)
Comment 5 retired 2013-02-26 01:20:16 UTC
No more feedback from bug reporter. Julien was not able to reproduce the issue. Maybe Gerard's guess with the .xls file is right. Setting to "notabug".

Michael, if this problem is still reproducible with LO 4.0 and using the open document format, feel free to re-open this bug.