Bug 85870 - Macros in spreadsheet saved by LibreOffice as xlsx don't execute when opened by LibreOffice
Summary: Macros in spreadsheet saved by LibreOffice as xlsx don't execute when opened ...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.3.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-04 18:34 UTC by David Miles
Modified: 2015-04-16 15:29 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of sheet with macro displayed (private data redacted) (28.63 KB, image/png)
2014-11-04 18:34 UTC, David Miles
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Miles 2014-11-04 18:34:55 UTC
Created attachment 108911 [details]
Screenshot of sheet with macro displayed (private data redacted)

A simple spreadsheet was created in LibreOffice. The data was sorted with column B descending and column A ascending. The spreadsheet was then saved in Microsoft Excel 2007/2010/2013 XML format. When the spreadsheet is opened with LibreOffice, the macros in column B do not display the correct values.
Comment 1 Tim Lloyd 2014-11-04 21:03:03 UTC
Hi David, can I just check the procedure pls?

1. Open Calc
2. Enter data into columns A & B
3. Select column A Data->Sort->Column A ascending
4. Select column B Data->Sort->Column B descending
5. Save as xlsx

I tried this with no problem on Fedora 21 but maybe I did not apply the procedure correctly.

Cheers
Comment 2 David Miles 2014-11-04 21:54:05 UTC
I haven't been able to create a simple spreadsheet to reproduce the problem either. I suspect that the sheet has been edited and modified many times over the last few years and some internal structures have gotten into an inconsistent state.

I was able to fix the spreadsheet by selecting and copying the entire original .ods sheet, then pasted that into a new blank sheet. After doing that, saving to a .xlsx seems to produce a file that behaves correctly.
Comment 3 Tim Lloyd 2014-11-05 22:53:38 UTC
as this is not easily reproducible I am closing it as "works for me".

David, feel free to reopen this if you don't agree with this interpretation.