Note:
- You don't necessarily have to create a specification by hand, you can also do it with code. In order to do this correctly, however, the person involved should be deep enough in the matter and know their tables well.
Create import specification of a DB in VB
- Exporting many tables (200?) with several GB of content and later re-importing them is more of a challenge. If the backend (of an unknown type) is based on a proper data model with relationships and set referential integrity, tables cannot be reimported in any order, the RI must be observed. If you have continued working with the database in the meantime, you cannot simply copy back data, but keys for the table links have to be reorganized. The level of difficulty is a lot higher than understanding a CSV. It was not for nothing that I made a point of considering the backup strategies of the database management system.
Instead the specific export is MANDATORY, at least for a nationalized version of Access
Otherwise the characters between dates, the characters between decimals, the characters to distinguish text from number, may be the same, and therefore make export impossible
"..with several GB of content and later re-importing.."
"..If the backend (of an unknown type) is based on a proper.."
"..and set referential integrity.."
"..It was not for nothing that I made a point.."
All these considerations are perfectly useless
You are assuming things that you cannot assume and have no relevance to answering the question asked
Create import specification of a DB in VB
Yes, working from code directly on the hidden tables that keep memory of the export specifications is one way to solve it
But once you understand exactly (or rather once I understand) what the problem is, there is a much simpler way to solve it
And the problem is that nationalized versions of Access may have inter-data, inter-numeric, inter-decimal characters, which are different from those used by the English/US version of Access