Created attachment 63044 [details] homemade character sheet for Dungeons and Dragons 3.5 or Pathfinder... The macro used in Cell D9 on the sheet labeled "Main" seems to trigger an error message. Upon re-inputting the macro name into the cell, there is no message, it is, however, obnoxious. The macro works flawlessly; the bug is simply that it gives an error message upon loading the file.
LibreOffice 3.5.4.2 Build ID: 350m1(Build:2) That's the information I get on my "About LibreOffice" screen. And the message is "BASIC Runtime Error. Property or method not found: Sheets."
Are you sure that this macro is included in attachment 63044 [details]? I can't find it in any category in Macro Organiser. Also function =levelxp() in not known.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO