Bug 41799 - Crash Saving Edited XLS with VBA Macro Code
Summary: Crash Saving Edited XLS with VBA Macro Code
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
3.5.0 Beta2
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-14 12:15 UTC by Scott M. Sanders
Modified: 2012-09-27 19:47 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
crashes on save if edited (97.50 KB, application/vnd.ms-excel)
2011-10-14 12:15 UTC, Scott M. Sanders
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Scott M. Sanders 2011-10-14 12:15:18 UTC
Created attachment 52347 [details]
crashes on save if edited

I have a file that if I just re-save it to a new XLS gives this warning but otherwise works OK:

"All changes to the Basic Code are lost. The original VBA macro code is saved instead."

But if I, for example, clear all the "data" rows (not those that looks like headers) and save as a new XLS, I get the error as above, then if I close LibreOffice, I get a document recover window, with no documents listed.

Attached is the first file.
Comment 1 Björn Michaelsen 2011-12-23 12:37:00 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 2 Scott M. Sanders 2011-12-30 07:58:39 UTC
This persists in 3.5.0beta2.
Comment 3 Scott M. Sanders 2012-09-27 19:47:06 UTC
It seems fixed in 3.6.2.1 RC 1, yay.