Description: see steps to reproduce Steps to Reproduce: 0. Take a look at the following codes. Make sure that ChrW is COMPATONLY_ Function. Make sure that Blue is NORMONLY_ Function. https://opengrok.libreoffice.org/xref/core/basic/source/runtime/stdobj.cxx?r=7283125c#136 https://opengrok.libreoffice.org/xref/core/basic/source/runtime/stdobj.cxx?r=7283125c#87 Steps A: 1. Open the attached ChrW.odt 2. Run Main() in ChrW.odt 3. Error is given as follows(Expected) BASIC runtime error. Sub-procedure or function procedure not defined. 4. Close the error dialog 5. Modify the source so that Option VBASupport is 1 6. Run Main() again 7. the macro runs without errors(Expected) 8. Modify the source so that Option VBASupport is 0 9. the runs without errors(UNEXPECTED) 10. Close all the LibreOffice applications, and then reopen ChrW.odt 11. We have VBASupport 0. When we run Main(), it gives me the same error(Expected) Steps B: 1. Open the attached Blue.odt 2. Run Main() in Blue.odt 3. Error is given as follows(Expected) BASIC runtime error. Sub-procedure or function procedure not defined. 4. Close the error dialog 5. Modify the source so that Option VBASupport is 0 6. Run Main() again 7. the macro runs without errors(Expected) 8. Modify the source so that Option VBASupport is 1 9. the runs without errors(UNEXPECTED) 10. Close all the LibreOffice applications, and then reopen Blue.odt 11. We have VBASupport 1. When we run Main(), it gives me the same error(Expected) Actual Results: Main()s unexpectedly runs without errors in A-9 and B-9 Expected Results: Main()s stop with errors in A-9 and B-9 Reproducible: Always User Profile Reset: No Additional Info: once methods are added to the candidate list, the runtime never removes the additions? https://opengrok.libreoffice.org/xref/core/basic/source/runtime/stdobj.cxx?r=7283125c#753
Created attachment 152777 [details] ChrW
Created attachment 152778 [details] Blue
errata: the real error message for Blue.odt in B-3 was BASIC runtime error. '35' Blue
Moving to NEW
Dear himajin100000, 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