Yes you did, I've made a new Sub and remarked yours, look at it to show the difference.
The data in the table wasn't "valid" so I've emptied it and have done the following:
Open the original json file, (the link you provide), marked all text in the window, copied it, and go into the database, clicked the button "Paste from Clipboard to table", then you can't paste it directly in the table only by code.
Copied some other text, (to clear the clipboard).
Then I clicked the button "jSON to CSV" to copy from the table and paste it into the "jSON to CSV Converter". And it convert perfect.
I couldn't open the second link you provide.
Database attached, but maybe I've misunderstanding something you're trying to do, so make it clear for me.
Thanks for this - it seems I didn't explain myself well
OK - first of all this is not meant to be a real application.
It was purely intended to :
a) confirm that long text (>32767) could be copied in full
b) check how long it took to paste to a second textbox
I've modified the code slightly to do b) & its instantaneous - see attached.
My next task is to find out why that isn't the case for this specific file in my real JSON parser database
I was aware the json to csv link would say it was an invalid file - that's because I retained your rich text example.
Sorry, I should have swopped it back to plain text or at least explained myself....
So reverting to plain text it of course works correctly.
NOTE: For anyone else reading this:
After copying to clipboard, click the
Clear Copied Text button to empty the
2nd textbox.
That does NOT empty the clipboard
If you then right click to paste in the normal way, it will fail because 'the text is too long to be edited'
If I remember correctly the length limit for that approach is 65536.
That's not a problem for me - I mention it in case anyone else reads this thread & wants to try it.
You said you couldn't open the second link - my JSON parser sample database.
Are you by any chance using
Access 2007?
I've had 2 other users report that it caused errors in that version.
There are 2 reasons:
a)
VBA references for MS Excel which are version specific & not automatically 'downgraded' to 2007 (Excel 12.0)
b) the
autoexec macro isn't compatible with A2007 - I think because it contains an If ... Else ... End If section
I've made lots of changes since that version of the db
In the latest version (not uploaded to the forum), I have amongst other things:
a)
removed the Excel reference - I'm now using late binding instead
b)
removed the autoexec macro & placed similar functionality in a splash form used at startup
So it SHOULD now work in A2007 but I don't have that version to test it against
Assuming you are using 2007, would you be willing to test the new version.
If so, please send me a private message (or email me using the link below) and I'll send you a link for this
Similarly for anyone else who may be interested in trying it out.
