Created attachment 142973 [details] Example file from Excel with password protected VBA macro If we want to keep your program (Macro/VBA Project) in safety in Microsoft Excel, we usually use the “VBAPROJECT Password” option to protect the VBA code. If we open the *.XLSM file with LibreOffice Calc the protection of the Project will disappear. Steps to reproduce: 1. Create a new spreadsheet with Microsoft Excel 2016/2013/2010 2. Open the Visual Basic window and create a simple visual basic Module. 3. Write a simple code in the module. 4. Click Tools on the Menu and choose “VBAProject Properties...” 5. Then choose “Protection”, check the “Lock project for viewing” checkbox and create a password to view project properties. Click OK. 6. Reload the *.XLSM file with Excel and check your VBA Project’s password protection. (It will work) 7. Open the file with LibreOffice Calc and check your VBA Project’s password protection. 8. Save as the file *.XLSM 9. Open it with Microsoft Excel Actual results: There is no password protection on the VBA Project. We can edit the modules. If we export the file with LibreOffice Calc and open it with Microsoft Excel the password protection will not be present. Four new workbooks icon appeared in the Microsoft Excel Objects folder at the VBA Project, after we reopen the exported *.XLSM file with Microsoft Excel. Expected results: The VBA Project password should not disappear after we open the *.XLSM file with LibreOffice Calc. After we reopen the exported file with Microsoft Excel, the Excel Object structure should be the same as in the original file. Version: 6.0.0.0.beta1+ Build ID: 29228e83df009cf76ac819ed024527be1092f065 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:libreoffice-6-0, Time: 2017-12-04_23:15:34 Locale: hu-HU (hu_HU); Calc: group threaded
Created attachment 142974 [details] The example file saved by Calc
Created attachment 142975 [details] The original file opened in Excel and Calc
Created attachment 142976 [details] The file saved by Calc in Excel. No protection anymore and new sheet objects
Confirmed. I can open macro in file without password in Version: 6.2.0.0.alpha0+ Build ID: c4c56de1b0e62ec866b519b2b24c5e805f0a86d3 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; and Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Setting to new per comment #4
Dear Gabor Kelemen, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Gabor Kelemen, 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