Hi,
I have a txt file. Each line in this file has the same width for each record (fixed width). I have created an import spec by importing the file for the first time, putting the break lines at the correct positions and then save the spec in the import table. So far, so good.
I have created a form with a button that should start the import, using DoCmd.TransferText.
The MT535Spec is the saved import specification (spelling has been double checked and is correct) for fixed width of each line.
The challenge: when manually import the same file using the saved import specification, the file is imported perfectly. Using the TransferText option MS Access tries to store the whole line of the text file in the first field of the table, instead of dividing the line into seperate fields.
Microsoft MSDN writes about "fixed width" files: SpecificationName - Optional Variant. A string expression that's the name of an import or export specification you've created and saved in the current database. For a fixed-width text file, you must either specify an argument or use a schema.ini file, which must be stored in the same folder as the imported, linked, or exported text file.
In my opinion I am supplying an argument, which would be "MT535Speci". Any ideas what I could be overlooking here?
--------
For Google indexing purpose: MS Access VBA importing txt file manually works fine, but using TransferText results in the whole line stored in the first field of a record.
I have a txt file. Each line in this file has the same width for each record (fixed width). I have created an import spec by importing the file for the first time, putting the break lines at the correct positions and then save the spec in the import table. So far, so good.
I have created a form with a button that should start the import, using DoCmd.TransferText.
Code:
DoCmd.TransferText acImportDelim, "MT535Spec", "tblDownloadExtern", strBestand, FalseThe challenge: when manually import the same file using the saved import specification, the file is imported perfectly. Using the TransferText option MS Access tries to store the whole line of the text file in the first field of the table, instead of dividing the line into seperate fields.
Microsoft MSDN writes about "fixed width" files: SpecificationName - Optional Variant. A string expression that's the name of an import or export specification you've created and saved in the current database. For a fixed-width text file, you must either specify an argument or use a schema.ini file, which must be stored in the same folder as the imported, linked, or exported text file.
In my opinion I am supplying an argument, which would be "MT535Speci". Any ideas what I could be overlooking here?
--------
For Google indexing purpose: MS Access VBA importing txt file manually works fine, but using TransferText results in the whole line stored in the first field of a record.
