Given the widespread use JSON as a data transport, we should have:
like we have:
There are a few libraries out there – replacing these with one or a few lines of code would be extremely useful.
Access in the API economy:
With the dramatic growth in cloud computing the need for seamless, fast integration (API’s) is in high demand. Taking advantage of these API’s within Access is brutal.
We need to be able to easily make these API calls and to be able to work with JSON, XML and other data types in Access. We need to be able to send and receive this data.
Not being able to use clients already built business logic via API’s makes it very hard to get approval for an Access front end.
Ben Sacheri commented
It's a no-brainer that Microsoft should add JSON support. It's an industry standard. What are they waiting for?
I've previously voted for similar suggestions:
a) add a JSON.dll
b) add an Access equivalent of Excel Power Query (Get & Transform)
However, its done, the important thing is that it is done.
In the meantime, I will continue / developing using my JATFA (JSON Analyse & Transform for Access) app which is available from http://www.mendipdatasystems.co.uk/json-analyse-transform/4594138310
Of course, if MS adds this functionality, my app may well become redundant
Krish J commented
Here is a free plugin that can import and export json. Have a look at my Github project. https://github.com/krishKM/VBA_TOOLS#importjson
Mark Burns commented
I would vote for this (if I had any votes left).
Karl Donaubauer commented
There is also Peter Bryant's older JSON suggestion: