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

Run-time error 3349 in Access2K to a Split DB

P: 2
I am getting a Run-time error 3349 when importing a .txt file into the front end of a DB (DB is split). If I use the same specs on the back-end I do not get the error. Is there some file limitation to what can be imported into a front end (linked) table? Note: I am ultimately trying to do the import through VBA in a form on the front end.

Any explanation or help greatly appreciated.
Dec 27 '07 #1
Share this Question
Share on Google+
4 Replies


P: 2
I am getting a Run-time error 3349 when importing a .txt file into the front end of a DB (DB is split). If I use the same specs on the back-end I do not get the error. Is there some file limitation to what can be imported into a front end (linked) table? Note: I am ultimately trying to do the import through VBA in a form on the front end.

Any explanation or help greatly appreciated.

I'm adding to my own issue. I have found that there seems to be a problem with the file specifications. If I use the original specs it works. If I 'Save As' the specs again (changing nothing) and only change the name of the specs. The newly saved specs do not work!!
Dec 27 '07 #2

MMcCarthy
Expert Mod 10K+
P: 14,534
We would actually need to see the code you are using for the import. There is no reason why there should be any difference in importing into the front-end or back-end.

Why are you changing the import spec. The point of having one is that it is saved and used thereafter. You may not realise there is a change happening but it sounds like there is.
Jan 8 '08 #3

P: 1
I got the same error (3349) when I try to import from Excel into a linked Access table.
-----
DoCmd.TransferSpreadsheet acImport, , _
"tblCurrentPrices", rstBatch!DirPath + rstBatch!Filename, True, rstBatch!Range
------
where tblCurrentPrices are linked to the front end app.
Any fix to this?
Reidar
Feb 12 '08 #4

MMcCarthy
Expert Mod 10K+
P: 14,534
I got the same error (3349) when I try to import from Excel into a linked Access table.
-----
DoCmd.TransferSpreadsheet acImport, , _
"tblCurrentPrices", rstBatch!DirPath + rstBatch!Filename, True, rstBatch!Range
------
where tblCurrentPrices are linked to the front end app.
Any fix to this?
Reidar
Link to the spreadsheet and append to the table.
Feb 12 '08 #5

Post your reply

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