Another demo of JSON Recordset (mimic the behavior of DAO.Recordset)

[arnelgp]

again, I asked AI to generate a json recordset class, that you can Apply Filter and Change Value
just as you can with a normal recordset.
this will become very handy if you have a consistent, single table, json file and you want the
ability to show it in the form and perform Edit and Filter to it.

Module1 has several test sample code.

 

[tvanstiphout]

The demo has 3 identical tables, one curiously named Employees. Can you shed more light on this?

 

[BlueSpruce]

The demo has 3 identical tables, one curiously named Employees. Can you shed more light on this?

I asked AI to generate . . .

. . . which caused the confusion.

 

[arnelgp]

the Ai keeps generating test code (for export to json) on employee table which i dont have, so i just copy xompany table and rename the copy as employee. New_employee table is created from test code to import back from a json string to New table, which I provide as new_Employees.

 

[AHeyne]

A good naming is often half the way.

 

[DickyP]

A fascinating thread but I fail to spot its usefulness. The whole point of JSON is to provide a fast and efficient system for basically unstructured data. I you read its Genesis it was devised as a way of avoiding the full panoply of XML to move data around on-line. We really shouldn't be running across it in a relational database.

 

[arnelgp]

The whole point of JSON is to provide a fast and efficient system for basically unstructured data

here's what AI has to say:

No, JSON is not unstructured data; it is considered semi-structured data because it has an internal organizing principle (key-value pairs) but lacks the rigid, pre-defined schema of a traditional relational database. It is more organized than unstructured data, which has no fixed format, but is more flexible than structured data.

Characteristics of JSON

• Semi-structured: It has a clear format with key-value pairs, objects, and arrays, making it easy to parse and understand.
• Flexible schema: Unlike structured data, not all JSON documents need to have the exact same fields, which allows for variations and evolution over time.
• Human-readable: Its format is easy for humans to read and write, which is why it is widely used for data interchange between applications, APIs, and configuration files.
  • Hierarchical: JSON can represent complex data by nesting objects and arrays within each other.

Examples of unstructured and structured data for comparison

• Structured data: Information that fits neatly into a table with predefined columns and rows, like a spreadsheet or a SQL database.
• Unstructured data: Raw, unfiltered d

 

[GPGeorge]

Spoiler:

A fascinating thread but I fail to spot its usefulness. The whole point of JSON is to provide a fast and efficient system for basically unstructured data. I you read its Genesis it was devised as a way of avoiding the full panoply of XML to move data around on-line.

We really shouldn't be running across it in a relational database.

That depends on what you mean by "running across it in Access".

Importing data from a Web API is one place where you'll find it, a lot.

And so on.

Where to find VBA tools for JSON: https://github.com/VBA-tools/VBA-JSON