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
As I run into edge cases and see others with TDF exports and Access's issues with XML #80#80, #305, #314, et. al., and I was thinking maybe another (also with its own caveats) way to do this is with modJSONConverter, and just export the table as JSON.
While this is no small feat, it is a nice balance of Human-readable and "We don't have to build all the tooling ourselves" inbetween land.
Thoughts? I'm experimenting with this for an internal application, and if I can get it to work, I'll put it up as a PR, but thought I'd toss out the idea in the case someone else has already tried it and found out it's a road to avoid.
The text was updated successfully, but these errors were encountered:
As I run into edge cases and see others with TDF exports and Access's issues with XML #80 #80, #305, #314, et. al., and I was thinking maybe another (also with its own caveats) way to do this is with
modJSONConverter
, and just export the table as JSON.While this is no small feat, it is a nice balance of Human-readable and "We don't have to build all the tooling ourselves" inbetween land.
Thoughts? I'm experimenting with this for an internal application, and if I can get it to work, I'll put it up as a PR, but thought I'd toss out the idea in the case someone else has already tried it and found out it's a road to avoid.
The text was updated successfully, but these errors were encountered: