By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,089 Members | 2,283 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,089 IT Pros & Developers. It's quick & easy.

Error: Field 'F1' doesn't exist in destination table. I've created import Specs but still get same error...

P: n/a
I'm automating the import of all text files into Access from a source
folder. I was getting the "Field 'F1' doesn't exist in destination
table" error, so I checked it out on the net and it said to create a
import specification. So I did this (InductionImport), and included it
in my code as below:

DoCmd.TransferText acImportDelim, InductionImport,
"ImportedInductionLots", CurrentPath & strfile, 0

I created the import specs as per Microsoft's explanation:
http://support.microsoft.com/default...b;EN-US;142186

I'm at a loss as to how to fix it... except just calling the field
names F1 - F12 and renaming them later (which is a lot of mucking
around and a bit untidy). From what I understand, this Spec should
rename the fields as they are imported to match the names in the table.
And when I did it manually, it worked...

All ideas appreciated...

Cheers

Reg

Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
DoCmd.TransferText acImportDelim, "MAIN Import Specification", "MAIN",
strFileToImport, True

Based on one I have that works, this is what I think is wrong - the
order of your arguments is wrong.

the second argument should be in quotes (the name of the import
specification). That should fix it. No, the import spec does not
rename any fields, it just maps values in the CSV file to the table.

Nov 13 '05 #2

P: n/a
DoCmd.TransferText acImportDelim, "MAIN Import Specification", "MAIN",
strFileToImport, True

Based on one I have that works, this is what I think is wrong - the
order of your arguments is wrong.

the second argument should be in quotes (the name of the import
specification). That should fix it. No, the import spec does not
rename any fields, it just maps values in the CSV file to the table.

Nov 13 '05 #3

P: n/a
Thankyou... works a charm.... excellent....

Nov 13 '05 #4

P: n/a
Thankyou... works a charm.... excellent....

Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.