Good morning folks. I am enthusiastically marking this thread "Solved".
First and foremost, an HUGE shout-out to
@Edgar_ . I remember when he joined AWF back in July, it seemed he came out of nowhere but immediately made an impact and I knew that AWF had gained another "Heavy Weight".
When I started this thread, he responded via PM with a single sentence: "Hey there, John, I saw you need a hand, I could take a look..." He wasn't the only one, but since he was first, and he had helped me in the past with this same issue, I responded and we set to work the next morning.
What he did was simply amazing. I will hit the high-spots and even share the db with an example of the JSON returned from the site if anyone is interested.
As I said earlier, the site actually uses a REST API to interface with the one that holds the raw data. He was able to see this in the HTML and once he gained access, made the following observations:
1. The site allows you to "pull" 100 records in JSON format at one time.
2. You only have an hour once your credentials (token) has been activated to get your business done.
Once the JSON is retrieved, he used a JSON Converter (VBA-JSON v2.3.1 (c) Tim Hall -
https://github.com/VBA-tools/VBA-JSON) to parse the data into a table. As of this morning, with 22,183 records, it took 1 hour and 18 mins to fetch and process this data. Fortunately, we anticipated this early on and to get around the 1 hour limit, we decided to break it up into 2 section; Fetch and Process.
The fetch routine goes and gets the JSON and stores it into a table with only two fields, an AutoNumber(PK) and LongText, for the record the average length of each JSON field is about 350k characters. The whole routine takes about 30min . The 2nd process then uses the JSON Converter and populates the appropriate table.
We know that eventually the fetch process will exceed the 1hour limit and he has offered to build in the ability to assign a new token
(how do folks know how to do this?!?) and I may take him up on that, but there are other and more efficient ways to deal with the data that come over i.e. there is no need to fetch archived records (17k at present) each and every time.
Missy (wife) had a Teams meeting with her bosses who had brought in a couple of IT folks to help us get clean data. It didn't last long since Edgar had already cracked that nut. After the meeting, her bosses' boss responded with a word: "FANTASTIC!"
Fantastic is an understatement. While we were working on this, I did my best to assist. Edgar was patient and painstakingly explained to me the JSON process while I muddled through it. Quite frankly, he would have it done a lot sooner had I not "helped". Even now he hits me up on WhatsApp with excited texts about process improvement.
@Edgar_ you are a Rock Star and as promised, what they "pay" me will be passed along and you have my "mark" in perpetuity.
Thank you...