error message in basic is confusing ,when I assign value that has same name as existing function when i execute basic code in which assign value that has same name as existing function,like sub test1 year = 1 end sub I got error "アクションはサポートされていません。無効なプロシージャの呼び出し" which means invalid procedure call. I think this error message is confusing.its better that the message is like "try to assign value that has same name as existing function" Version: 7.1.1.2 (x64) / LibreOffice Community Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: CL
Message in english: Action not supported. Invalid procedure call. Message looks good to me, leaving unconfirmed.
Alain: what do you think? Is it possible to specify the error message like this?
Ideally, such a use should be detected at compile time. Instead a runtime error number 5 - Invalid procedure call - is returned; prepended with "Action not supported." text that isn't a documented error message. Indeed, One may expect some clearer message such as, but not limited to: 951 Unexpected symbol 'year' 958 Sub procedure or function procedure already defined 968 Symbol already defined differently 1004 Error executing a method I don't have a M$ environment to examine VBA behaviour at compile time and during runtime. Someone holding M*Office needs to confirm this report.
M$-Office shows a compiling error with "argument is not optional"
Hello, It's been a while since this issue was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear tripod312, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping
Dear tripod312, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp