Bug 98845 - Scripting.Dictionary.Item(New Collection)
Summary: Scripting.Dictionary.Item(New Collection)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
5.1.1.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-23 15:51 UTC by DM
Modified: 2024-05-06 03:15 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
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 DM 2016-03-23 15:51:00 UTC 
This (and any permutation of it I've tried) fails on the last (oColB =) line variously with a crash or type fail; Win10:-

Dim o As Object, oCol As Object,oColB As Object
Set o=New Scripting.Dictionary
o.Add "T", New Collection
Set oCol = o.Item("T")
Set oColB = o.Item("T")

Cheers,
David
Comment 1 DM 2016-03-23 16:11:16 UTC 
Putting New Collection into a variable first I get instead of a crash:-

Inadmissible value or data type.
Invalid number of arguments.

The problem also occurs if I use a New Scripting.Dictionary instead of New Collection

d
Comment 2 DM 2016-03-23 16:38:11 UTC 
This also seems to fail on w= suggesting the act of reading a non-simple variable jeopardises any further reading. If Array() is changed to "a" then w= works fine. d


Dim o As Object,v,w
Set o=New Scripting.Dictionary
o.Add "A", Array()
v= o.Item("A")
o.Add "B", "b"
w= o.Item("B")
Comment 3 Buovjaga 2016-04-03 13:40:41 UTC 
Can you give the complete code we need to run it?

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the code.
Comment 4 DM 2016-04-04 13:21:47 UTC 
To explain the top post a bit better - you
1. create a new spreadsheet
2. create a new module
3. ensure the code as below
4. with the insertion point in Main() use F5 to run it. It will fail on Set oColB (but not on Set oCol).
Same problem if instead of a New Collection you'd used various other complex items, including arrays. If oCol/oColB are kept as variants and Set omitted the same occurs, but usage of an simple literals (eg a number or string) is fine (eg using o.Add "T",5 is fine).
hope that helps!
d

--------- FAILS ----------

Sub Main

Dim o As Object, oCol As Object,oColB As Object
Set o=New Scripting.Dictionary
o.Add "T", New Collection
Set oCol = o.Item("T")
Set oColB = o.Item("T")

End Sub

--------- ALSO FAILS ----------

Sub Main

Dim o As Object, oCol,oColB
Set o=New Scripting.Dictionary
o.Add "T", New Collection
oCol = o.Item("T")
oColB = o.Item("T")

End Sub
Comment 5 Buovjaga 2016-04-08 12:12:31 UTC 
I still get the same problem:
Object not accessible.
Invalid object reference.

Pointing to this line:
Set o=New Scripting.Dictionary
Comment 6 DM 2016-04-08 13:12:52 UTC 
It's normally a windows object normally available for use by things like VB and VBScript, so I guess it may be it will only work on windows (if you're not using it? here, Windows 10).
I'm not sure how LibreOffice uses, interfaces or emulates it, but the question is why the first read of (complex) data works, but the second doesn't. Obviously when called from other programs it doesn't have such an issue.

d
Comment 7 Buovjaga 2016-04-12 10:56:34 UTC 
It fails for me on Set oCol = o.Item("T")
BASIC runtime error.
Object variable not set.

Win 7 Pro 64-bit, Version: 5.1.2.2 (x64)
Build ID: d3bf12ecb743fc0d20e0be0c58ca359301eb705f
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
Locale: fi-FI (fi_FI)
Comment 8 QA Administrators 2018-05-05 02:40:38 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2020-05-05 03:44:07 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2022-05-06 03:42:29 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2024-05-06 03:15:08 UTC 
Dear DM,

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