Description: Calc can open an Excel xlsm file with Range macro, and work normally. However, after Save locally, Close the file and re-Open in Calc, the macro does not function any more. Steps to Reproduce: 1.File Open the attached EXCEL file with Range processing macro and Enable macro 2.Check the value of both the Cell A2 and the Cell B2 change when active cell switching around A4,A5 and A6, which meaning the macro works normally. 3.Save the file -> Close the file -> re-Open the file in Calc Actual Results: The macro in the saved file fails to work. Expected Results: the value of both the Cell A2 and the Cell B2 change when active cell switching around A4,A5 and A6, as I open the Excel generated file the first time. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: SpreadsheetDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes
Created attachment 169828 [details] xlsm file generated using Excel I have checked Calc 6 and 7, nor of them working.
Created attachment 169829 [details] The macro in this saved file does not function any more.
Reproduced. Already in oldest of Linux 6.3 bibisect repo. Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 04f9a8957c04b8c5abaa58140328d2c83381f4ff CPU threads: 2; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: threaded Jumbo Arch Linux 64-bit Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 896c097f1fa4bc9d2e5ea87a696c125bb335ecac CPU threads: 8; OS: Linux 5.16; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Jumbo Built on 3 March 2022
Dear zexcel, 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