Bug 34637 - Calc relative links not all saving
Summary: Calc relative links not all saving
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.3.0 release
Hardware: x86 (IA32) Windows (All)
: high blocker
Assignee: Kohei Yoshida
URL:
Whiteboard: target:3.4
Keywords:
: 35029 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-02-23 12:45 UTC by ron gregor
Modified: 2011-03-10 22:28 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
zip file with 3 test spreadsheets (28.68 KB, application/x-zip-compressed)
2011-02-23 12:45 UTC, ron gregor 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ron gregor 2011-02-23 12:45:59 UTC 
Created attachment 43727 [details]
zip file with 3 test spreadsheets

We have sheets that have several relative links to another sheet but not all are saving. When you update the links all the values are correct. Save the sheet and close. Open the sheet and only the first link is valid the rest are zero's. The attached sheets are for example. File A has 3 links (c4, c5, c6) to upgrade. Open File A and select update and then E13=13.825. Save the sheet and close. Open File A and C5 and C6 are 0 and E13=1.250. This becomes a problem when File B tries to link to the value E13 in File A. In our real set up we have several "File A's" that File B summarizes for us. The only way I could fix this was to install Openoffice 3.3 which why I called it a blocker unless someone can figure out how to work around links not saving.
Thanks, Ron
Comment 1 ron gregor 2011-02-23 12:51:20 UTC 
Second sentence should end "values are NOT correct" sorry - new to this and not sure how to update information.
Comment 2 ron gregor 2011-02-23 13:03:17 UTC 
Ingore comment 1 - original post is correct.
Comment 3 ron gregor 2011-02-24 06:32:28 UTC 
I just tested verion 3.3.1.2 and the problem exists in that version also.
Comment 4 Kohei Yoshida 2011-03-03 17:05:45 UTC 
Thanks for your bug report.  This has been fixed in 3.4.  Unfortunately the change is very invasive that we can't backport this to the 3.3.x line.
Comment 5 Andrew Dodsworth 2011-03-10 22:28:19 UTC 
*** Bug 35029 has been marked as a duplicate of this bug. ***