Issue 109495 - Backward compatibility issue - file saved with 3.1 version not opened correctly into 3.2
Summary: Backward compatibility issue - file saved with 3.1 version not opened correct...
Status: CONFIRMED
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 3.2
Hardware: Mac Mac OS X, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2010-02-21 16:36 UTC by dragoshenron
Modified: 2013-01-29 21:52 UTC (History)
3 users (show)

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


Attachments
Spreadsheet not opening correctly with 3.2 (38.86 KB, application/vnd.oasis.opendocument.spreadsheet)
2010-02-21 16:38 UTC, dragoshenron
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description dragoshenron 2010-02-21 16:36:59 UTC
I found a (major) issue with my file.
I create a spreadsheet to manage my bank account and categorize my expenses.
I used the function EOMONTH as well as IF and SUMPRODUCT.
Working perfectly in version 3.1, I update openoffice to 3.2.
I found all cells with the error #values.

Can you help me? I'd like to upload the file so you can check what is wrong.

Thanks in advance
Comment 1 dragoshenron 2010-02-21 16:38:02 UTC
Created attachment 67966 [details]
Spreadsheet not opening correctly with 3.2
Comment 2 dragoshenron 2010-02-21 16:40:59 UTC
Look into the sheet 'summary'.
Opening with 3.1 gives the summary of the values reported in the 'CC' sheet.
Opening with 3.2 gives #VALUES error
Comment 3 Regina Henschel 2010-02-21 18:39:49 UTC
That is the intended new behavior for converting strings.
See i5658 desc215 for details.
You have to correct your spreadsheet to unambiguous formulas. 

You can avoid any problems with date strings and locals, if you use
=EOMONTH(DATE(2008;10;1);C2-1)
instead of
=EOMONTH("01/10/2008";C2-1)
assuming 1 is the day and 10 is the month.

Only strings containing ISO formats are converted now, to avoid ambiguity. You
can still use 
=EOMONTH("2008-10-01";C2-1)

I don't know, whether it is possible to convert date strings to ISO format
automatically, guessing the local from the cell number format language for
example. I tend to set this issue to "WONTFIX", but a developer should comment.
Comment 4 dragoshenron 2010-02-21 19:11:30 UTC
Thank you regina!

If I have only to change the eomonth function it might be ok.
For sure an import function to convert files from 3.1 to 3.2 to solve this
compatibility is more than welcome :)
Comment 5 jbf.faure 2010-02-21 20:38:14 UTC
Add me to cc.