Bug 134714 - VBA Macro: Range names don't work
Summary: VBA Macro: Range names don't work
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.1 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Macro-VBA
  Show dependency tree / graph
 
Reported: 2020-07-10 11:22 UTC by Xisco Faulí
Modified: 2023-03-18 03:27 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
sample file (12.25 KB, application/vnd.ms-excel.sheet.macroEnabled.12)
2020-07-10 11:22 UTC, Xisco Faulí 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Xisco Faulí 2020-07-10 11:22:24 UTC 
Created attachment 162878 [details]
sample file

Steps to reproduce:
1. Open attached document
2. Run checkRange macro

-> BASIC runtime error '1'. Instead, value of A3 should be pasted in A1

Reproduced in

Version: 7.1.0.0.alpha0+
Build ID: 12bfedfac3b141fe6c91b0e5ae5b3fb2ba817c48
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

and

Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Comment 1 Xisco Faulí 2020-07-10 11:23:00 UTC 
@Eike, I thought you might be interested in this issue
Comment 2 himajin100000 2020-07-10 11:41:25 UTC 
FYI:

Sub checkRange()
    Cells(1, 1) = Range("MOISANNEE").Value
End Sub

instead of 

Sub checkRange()
    Cells(1, 1) = Range("CRAM!MOISANNEE").Value
End Sub

works
Comment 4 Xisco Faulí 2020-07-10 16:05:46 UTC 
moving to NEW based on comment 2
Comment 5 QA Administrators 2023-03-18 03:27:56 UTC 
Dear Xisco Faulí,

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