Bug 91008 - FILEOPEN: XLS - VBA code lost during import
Summary: FILEOPEN: XLS - VBA code lost during import
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: filter:mso97
Keywords: filter:xls
Depends on:
Blocks: Macro-VBA
  Show dependency treegraph
 
Reported: 2015-05-02 02:16 UTC by Yousuf Philips (jay) (retired)
Modified: 2024-06-05 03:20 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
XLS file with VBA (66.00 KB, application/vnd.ms-excel)
2020-11-11 18:45 UTC, Buovjaga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2015-05-02 02:16:02 UTC
Steps:
1) Open http://www.exinfm.com/excel%20files/implprem.xls which has VBA
2) Save it as a new file
3) Open it in Excel and it wont warn you about VBA in the file

Version: 5.0.0.0.alpha1+
Build ID: 59adad74084e9281887e3f78a225794f37b784d7
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2015-04-29_12:34:23
Comment 1 raal 2015-05-02 06:21:07 UTC
I can confirm with Version: 5.0.0.0.alpha1+
Build ID: 59adad74084e9281887e3f78a225794f37b784d7
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-04-29_12:40:39
Comment 2 Robinson Tryon (qubit) 2015-12-09 16:51:20 UTC Comment hidden (obsolete)
Comment 3 Markus Mohrhard 2016-04-12 13:29:51 UTC
VBA export is implemented in 5.1.
Comment 4 Yousuf Philips (jay) (retired) 2016-04-12 16:05:45 UTC
Roundtrip didnt work in master.

Version: 5.2.0.0.alpha0+
Build ID: 02fb3fd0533222dfea5b6b9232425a5e28cd340f
CPU Threads: 2; OS Version: Linux 4.2; UI Render: default; 
TinderBox: Linux-rpm_deb-x86@71-TDF, Branch:master, Time: 2016-03-29_06:02:35
Locale: en-US (en_US.UTF-8)
Comment 5 Markus Mohrhard 2017-04-23 21:23:25 UTC
The macro is lost during import and not during export.
Comment 6 Yousuf Philips (jay) (retired) 2017-04-23 21:56:08 UTC
(In reply to Markus Mohrhard from comment #5)
> The macro is lost during import and not during export.

Okay changing description accordingly.
Comment 7 QA Administrators 2018-07-03 02:39:35 UTC Comment hidden (obsolete)
Comment 8 Buovjaga 2020-11-11 18:45:20 UTC
Created attachment 167214 [details]
XLS file with VBA

Still confirmed

Arch Linux 64-bit
Version: 7.1.0.0.alpha1+
Build ID: 3d3180115be3b87e76189aea2031f0caa735dbb3
CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 11 November 2020
Comment 9 himajin100000 2022-06-05 12:42:43 UTC
FWIW when I opened this file in Excel, it gives me the message given below:

https://mskb.pkisolutions.com/kb/926430
Comment 10 QA Administrators 2024-06-05 03:20:03 UTC
Dear Yousuf Philips (jay) (retired),

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug