https://bugs.documentfoundation.org/show_bug.cgi?id=98845
--- Comment #9 from QA Administrators ---
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 o
https://bugs.documentfoundation.org/show_bug.cgi?id=98845
--- Comment #8 from QA Administrators ---
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retes
https://bugs.documentfoundation.org/show_bug.cgi?id=98845
Buovjaga changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://bugs.documentfoundation.org/show_bug.cgi?id=98845
--- Comment #6 from DM ---
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
https://bugs.documentfoundation.org/show_bug.cgi?id=98845
--- Comment #5 from Buovjaga ---
I still get the same problem:
Object not accessible.
Invalid object reference.
Pointing to this line:
Set o=New Scripting.Dictionary
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.documentfoundation.org/show_bug.cgi?id=98845
DM changed:
What|Removed |Added
Status|NEEDINFO|UNCONFIRMED
Ever confirmed|1
https://bugs.documentfoundation.org/show_bug.cgi?id=98845
Buovjaga changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDINFO
CC|
https://bugs.documentfoundation.org/show_bug.cgi?id=98845
--- Comment #2 from DM ---
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.Dict
https://bugs.documentfoundation.org/show_bug.cgi?id=98845
--- Comment #1 from DM ---
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
C