Description: Hitting either of the "Run Macro" or the "Assign..." buttons immediately forces LibreOffice to crash, then it wants to recover the file I was working on. I can record and edit macros, but can only run them from within the editor. They won't run outside of it and I can't apply them to Base form buttons. Keyword: EDITING Steps to Reproduce: 1. Hit the "Run Macro" or the "Assign..." buttons. 2. Watch LibreOffice crash every single time. 3. Try to remember that this is a volunteer created project. Actual Results: I'm able to record and edit macros, and run them from within the editor, but when I'm using Base, after creating a button on a form, then using its Control Properties "Events" tab, then going to the "..." by "Mouse Button Pressed," then clicking on "Run Macro...", it just causes LibreOffice to immediately crash. If I open it again, then it asks if I want to restore the database I was working on. The same thing happens if I go to the Editor via the Tools menu, then go to the Tools menu again, and choose "Select Macro", then navigate to the "Module1" of my database, then click on "Assign..." In the main LibreOffice landing page, I went to the Tools menu, then Options, then Advanced, then to the Expert Configuration window, and found something very strange that I think could be causing the problem: Preference Name: org.openoffice.Office.UI.Commands:LabelType['.uno:RunMacro'] Property: Label Type: string Value: R~un Macro... Should the Value actually say "Run Macro" instead of "R~un Macro"? Also, when I search in that window for "macro" a bunch of different settings show up which don't really make a lot of obvious sense. I did find the one for macro recording, so I set that to "true" and there are some others that have to do with disabling things like an infobar for it, but that seems to be neither here nor there. I just want to be able to apply my macro to a button I put on a form in Base. I don't understand what the problem is, nor why it should be this complicated. I've made sure that I have the latest JRE instealled, I've added that to the Advanced section under Tools, then Options. I've made sure that everything (LibreOffice, JRE, and Windows 10 Pro) is 64-bit and updated. I tried doing the Repair option for uninstalling, but that did not work. I then uninstalled, removed the remaining files (uncluding those that RevoUninstaller's advanced uninstaller still missed), and that didn't fix the problem either. I saved the user folder as user_old, to force LibreOffice to create a new one (set everything to default settings), and that didn't help either. When I re-open my database, LibreOffice does ask me if I want to enable macros, and yet nothing ever gets applied to that button (not shocking, but this seems weird to me, that it would ask me that when nothing got applied to anything in the database itself). What am I missing here? What should I be doing to fix this? Expected Results: Everything crashes, nothing seems to work the way it should, and I'm just getting confused and frustrated by this. Reproducible: Always User Profile Reset: Yes Additional Info: I'm not some great programmer and I might not understand everything you say if you make it more technical than it has to be. Thanks in advance for understanding. Version Info: Version: 25.2.1.2 (X86_64) / LibreOffice Community Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49 CPU threads: 12; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
Oh, sorry. Expected results: I expect that when I try to run or assign a macro when I'm not inside the macro editor, then it will do what I'm telling it to.
I even tried (after posting the above) doing another 100% clean install of the latest Beta version, and it's doing the same exact thing. I'm about to try an archived version from 2015, because of a YouTube video made by a really great LibreOffice teacher, where that version worked for him in the video. I'm hoping that will work for me too, though I'm obviously on a different operating system version than he was. "LibreOffice Base (62) Standalone Switchboard" https://youtu.be/U4cIpMxklhA?si=ZcYJbSJee_yTjU5t That video shows him successfully doing, with the macros for the buttons, what I'm trying to do for my project. It was while I was working on my Base project that I started having trouble with LibreOffice's macros in general. It's a problem with the general LibreOffice software though. It's not specific just to Base.
Well, after trying "LibreOffice_5.1.0.1_Win_x64.msi" from the archives, I was finally able to assign the macro to the button, but now the entire form refuses to load after being saved and closed. I get the following error when trying to either open or edit it: "SfxBaseModel::loadFromStorage: 0xf26(Error Area:Io Class:Format Code:38)" That's both in the archived version of LibreOffice and the Beta version (25.2.2.2), which I've also been trying out for this (and which refused to run or assign the macros in the same manner as the current stable version). I'm taking a look at the following, to see if I can figure this stuff out: https://forum.openoffice.org/en/forum/viewtopic.php?p=507891 It sounds like maybe V. 6 or 7 would be a better option? Either way, whatever the solution to all of this is, please implement it in V. 25.2.2.2! If there's a workaround that can come sooner, then please tell me about it so I can implement it on my side of things!
Version 6 did the same thing as version 5 for opening the form, but did allow me to run the macro from the macro editor. Version 7 gave the following error while I tried to run the macro from the macro editor: "BASIC runtime error. An exception occurred Type: com.sun.star.lang.WrappedTargetException Message: TargetException: Type: com.sun.star.sdbc.SQLException Message: [OOoBase] No connection to the database exists." It gave me the following when I tried to open the form: "SfxBaseModel::loadFromStorage: 0xf26(Error Area:Io Class:Format Code:38)" It seems like version 6 is my best bet for now. I still need help with this though. I don't like knowing that the current, stable version is misbehaving the way it is (at least for me). I would rather be using it and upcoming versions instead.
Ok then! I used version 6 to recreate the form with the button on it that I want programmed, and that worked out just fine, once I had the settings fixed up (as mentioned previously, for the latest, stable version). Here are the Version specs that are working for me, on Windows 10 Pro: "Version: 6.4.4.1 (x64) Build ID: b50bc319eca5cd5b66fbfe2ebd0d3bd1eed099b5 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded" I did have to recreate the form though. The original, created in the most recent, stable version, wouldn't open, once the macro was applied and then saved (in version 5). Whatever the difference is between those two versions, it's version 6 that has what I needed to solve this issue, at least for now! I'll come back and notate any other problems that crop up with this.
Please can you attach test file for reproducing the bug? Thank you.
(In reply to raal from comment #6) > Please can you attach test file for reproducing the bug? Thank you. Thanks for offering to help me out with this! I don't have the foggiest idea how to do that. What test file? Without knowing what you mean by that, or how to do that, then my best guess is that it would help if you were to load up a standard PC with Windows 10 Pro, with no fancy changes made to the OS itself (nothing beyond cosmetic changes to its appearance), then load up your software and heave at it, I guess. You should be able to see what I mean. I'm glad to answer questions about my OS configuration (maybe there's something I don't remember doing to it over the years), if you tell me where to find the information you're looking for about that. I just don't know how to make a test file for you, or where to find that in the software folders, or whatever.
Hello, I mean Base file, where a tester can hitting either of the "Run Macro" or the "Assign..." buttons and see the crash. Thanks.
(In reply to raal from comment #8) > Hello, I mean Base file, where a tester can hitting either of the "Run > Macro" or the "Assign..." buttons and see the crash. Thanks. Are you asking me to create a test Base file, with a table, a form, and a macro for a button on the form, even though I can't attach the macro to it?