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

TransferText Error!

P: 8
Hi All,

Im having a bit of problem importing a text file into my database. The database is split into two (FE and BE). The code WAS working fine - however has now stopped working throwing up the errors below.

The bit of code causing the problem is:

DoCmd.TransferText acImportDelim, , "tbl_TEMP_Import", FileLength, True

FileLength contains the path to the file, and tbl_TEMP_Import is the table it needs importing into.

The error I am getting is one of two, either:
1) Numeric Field Overflow 3349
2) Cant remember the exact details but was something like "Property Not Found".

Any ideas? As I said, the code was working fine, I've tried and compact and repair and its not sorted it.

Thanks, Shane
Mar 20 '08 #1
Share this Question
Share on Google+
4 Replies


Expert Mod 2.5K+
P: 2,545
...
DoCmd.TransferText acImportDelim, , "tbl_TEMP_Import", FileLength, True
...The error I am getting is one of two, either:
1) Numeric Field Overflow 3349
2) Cant remember the exact details but was something like "Property Not Found".
Hi. I notice that you are not using a file import specification; a potential source of the error is an imported field treated as a numeric, say, which contains a text value or other non-numeric value part way into the import. This will cause errors as a result of non-compatibility of the data. Without an import specification Access will interpret the data types from the first lines it encounters.

I have quoted the TransferText help file note on the import specification below:
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. To create a schema file, you can use the text import/export wizard to create the file. For delimited text files and Microsoft Word mail merge data files, you can leave this argument blank to select the default import/export specifications.
-Stewart
Mar 20 '08 #2

P: 8
Thanks Stuart - I will take a look at that and see if it fixes it.

Thanks, Shane
Apr 1 '08 #3

P: 8
Tried this but still getting the same error. I have tried looking around on the net and a few other people seem to get the problem after splitting the database in 2 but nobody seems to know a solution.

Anybody got any ideas?
Apr 8 '08 #4

P: 8
Sorted it - as it turned out the file I was trying to import had changed slightly. Fixed it, thanks again for your help Stewart.
Apr 8 '08 #5

Post your reply

Sign in to post your reply or Sign up for a free account.