You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a macro that parses a JSON using this library.
The JsonConvertor works fine.
However, when i try to access an element Dict(key), it works on my 32bit Excel 2016 (on my 64bit laptop), but when I do the same on the 64bit Excel 2016 (on a 64bit laptop), I get the error
Run-time error '458': Variable uses an Automation type not supported in Visual Basic.
Note that the JsonConvertor works (as in doesn't throw any error) in both version of Excel, it is just the accessing items that causes the problem.
I tried stepping into the code line by line with my 32bit and 64bit excel side by side. The difference is the line dict_pDictionary.item(key) in Public Property Get item(key As Variant) As Variant, where the the working 32bit returns a Variant/Object/dictionary whereas the 64bit returns a Variant/Integer with the value <Internal error>
So maybe this is a VBA-Dictionary issue? I am not sure.
The text was updated successfully, but these errors were encountered:
Hi there,
I have a macro that parses a JSON using this library.
The JsonConvertor works fine.
However, when i try to access an element
Dict(key)
, it works on my 32bit Excel 2016 (on my 64bit laptop), but when I do the same on the 64bit Excel 2016 (on a 64bit laptop), I get the errorRun-time error '458': Variable uses an Automation type not supported in Visual Basic.
Note that the JsonConvertor works (as in doesn't throw any error) in both version of Excel, it is just the accessing items that causes the problem.
I tried stepping into the code line by line with my 32bit and 64bit excel side by side. The difference is the line
dict_pDictionary.item(key)
inPublic Property Get item(key As Variant) As Variant
, where the the working 32bit returns a Variant/Object/dictionary whereas the 64bit returns a Variant/Integer with the value<Internal error>
So maybe this is a VBA-Dictionary issue? I am not sure.
The text was updated successfully, but these errors were encountered: