G
Guest
Thanks for taking the time to read my question.
I have to import text (.csv) files to tables in my database. The trick is,
the user can select what file they want to import into what table. It's ok
if the files to import are speradsheets as docmd.TransferSpreadsheet takes
care of it, but if they are text files (docmd.TransferText) you need an
Import Specification (found when you import a file and then click on the
'Advanced' button).
DoCmd.TransferText acImportDelim, ImportSpecificationName, tblName,
FileName, True
If I could buid this on the fly for the table that would be great. If I
could build it once through code, and save it, then check if the table has an
Import Specification associated to it, that would be fine too. The user can
make and delete some tables. That is why I need this part to be flexible. I
can't have the user import Excel files because of the 65000 row limit. Some
of the files to be imported will be larger than that.
Thanks again for your help,
Brad
I have to import text (.csv) files to tables in my database. The trick is,
the user can select what file they want to import into what table. It's ok
if the files to import are speradsheets as docmd.TransferSpreadsheet takes
care of it, but if they are text files (docmd.TransferText) you need an
Import Specification (found when you import a file and then click on the
'Advanced' button).
DoCmd.TransferText acImportDelim, ImportSpecificationName, tblName,
FileName, True
If I could buid this on the fly for the table that would be great. If I
could build it once through code, and save it, then check if the table has an
Import Specification associated to it, that would be fine too. The user can
make and delete some tables. That is why I need this part to be flexible. I
can't have the user import Excel files because of the 65000 row limit. Some
of the files to be imported will be larger than that.
Thanks again for your help,
Brad