search

joyfullservice / msaccess-vcs-addin

Synchronize your Access Forms, Macros, Modules, Queries, Reports, and more with a version control system.
Other
198 stars 39 forks source link

How to export the data of the tables with the export all source file flow #437

Open sotalvaro opened 10 months ago

sotalvaro commented 10 months ago

I need export the data of the tables with all the files when I export all the source files

joyfullservice commented 10 months ago

@sotalvaro - This question comes up occasionally, so I have added some details to the FAQs page. You can also read a more detailed discussion in #250. Hope that helps!

sotalvaro commented 10 months ago

@sotalvaro - This question comes up occasionally, so I have added some details to the FAQs page. You can also read a more detailed discussion in #250. Hope that helps!

Thanks adam, Can you explain a little bit more whats is the difference between xml option or tab delimited?

joyfullservice commented 10 months ago

If your goal is to easily read simple text data in version control, tab delimited might be a good choice. (For example, a table with simple key-value pairs of configuration settings.)

If you want to load the data back into the system during a build, XML is a much more robust choice. With the improved indenting and layout enhancements added this year, readability has been greatly improved in the XML files.

I find that XML is usually the better choice for almost all of my personal use cases, but feel free to try out both and see what works better for what you are trying to accomplish. (Select Tab Delimited, run an export, then change to XML and run an export to see the difference.)

If you haven't already seen it, you will probably also benefit from the page in the Wiki that describes the add-in options. (Note that some of the newest V4 options are not yet documented here, but it should help in understanding some of what is available.)

sotalvaro commented 10 months ago

This is because the both methods produces me an error in the process of build the application

sotalvaro commented 10 months ago

If your goal is to easily read simple text data in version control, tab delimited might be a good choice. (For example, a table with simple key-value pairs of configuration settings.)

If you want to load the data back into the system during a build, XML is a much more robust choice. With the improved indenting and layout enhancements added this year, readability has been greatly improved in the XML files.

I find that XML is usually the better choice for almost all of my personal use cases, but feel free to try out both and see what works better for what you are trying to accomplish. (Select Tab Delimited, run an export, then change to XML and run an export to see the difference.)

If you haven't already seen it, you will probably also benefit from the page in the Wiki that describes the add-in options. (Note that some of the newest V4 options are not yet documented here, but it should help in understanding some of what is available.)

Hi Adam, I have a question for the JSON of the tables I have 9 linked tables that have multiples primary keys how can I export the tables in the folder of structure "tbldefs" with this primary keys, because I check the file and export with any primary key

image

@hecon5 or you man, may you have an idea for that? This will be a incredible help for me, thanks a lot.

hecon5 commented 8 months ago

When you say multiple PKs, do you mean Foreign Keys? The data export won't care about the state of primary/foreign/data state. Also, table data is exported into the folder tables and not tbldefs. Tbldefs is the folder for the table definitions. See wiki Export/Import Page for more details.