You are thinking perhaps a little bit narrowly here. If you want to carry the data physically, "sneakernet" will work fine. Put the back-end file itself on a thumb drive and do your linking from the target DB so you can manually pull the data over. A 4 GB thumb drive (these days) is dirt cheap and an Access BE can't exceed 2 GB so it should all fit. Creating non-Access intermediate files may well be the cause of some of those unexpected text line-breaks. We have a phrase that may apply here. "If you can't bring Muhammad to the mountain, bring the mountain to Muhammad."
".. Put the back-end file .."
I wrote about 'linked tables' but we are not talking about Access file as a data container
The data is contained in a db server, which Access accesses via odbc
The focal point is not how to transfer data from one db to another
I can already do this now using the classic administration tools of the used db server
My question is how to create, if it is possible to do so, a procedure in vba that allows me to put all the data contained in a db table into a file, and then a procedure that allows me to use this file to restore the data table on other db, without losing characters
Having already tried various native Access procedures such as Docmd.TransferText and similar to export the contents of a source table to an intermediate file, and having found that after importing the data, the destination table is not identical to the source table, so I set the question hoping that there was some particular option in the native Access data export/import procedures that would allow to overcome these problems
But I understand that native procedures only work for the simplest cases, and therefore to be sure that the destination table is identical to the source table, the only possibility is to create customized code