Bug 157832

Summary: Property and Method error when Macro Name same as Object
Product: LibreOffice Reporter: Martin Brieger <martin.brieger>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INSUFFICIENTDATA    
Severity: normal CC: ilmari.lauhakangas
Priority: medium    
Version: 7.6.2.1 release   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:

Description Martin Brieger 2023-10-20 00:36:55 UTC
When a Macro has the same name as an Object, an Error is issued that Property or Method can not be found.

To re-create, save a Macro (File) with the name ComboBox and have a Macro with the same Object name. The Debugger shows the right Properties, but the Macro issues the Error that Property or Method can not be found. i.e. ComboBox.SelectedText

Apparently there is no distinction between the Module Name and the Object Name when a Macro is executed. It doesn't matter, if the Object is in a different Macro (sub routine).
Comment 1 Werner Tietz 2023-10-20 08:25:17 UTC
Hallo

please attach a Example-doc with Combobox and Makrocode

What do you expect? BASIC can't even distinguish between upper and lower case.
Comment 2 QA Administrators 2024-04-28 03:16:21 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2024-05-29 03:14:53 UTC
Dear Martin Brieger,

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