Run-time error 3349 in Access2K to a Split DB

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Melancholy Man
    New Member
    • Dec 2007
    • 2
    #1

    Run-time error 3349 in Access2K to a Split DB

    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.
    Tags: None
    • Melancholy Man
      New Member
      • Dec 2007
      • 2
      #2
      Originally posted by Melancholy Man
      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!!

        Comment

        • MMcCarthy
          Recognized Expert MVP
          • Aug 2006
          • 14387
          #3
          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.

            Comment

            • Reidar
              New Member
              • Feb 2008
              • 1
              #4
              I got the same error (3349) when I try to import from Excel into a linked Access table.
              -----
              DoCmd.TransferS preadsheet acImport, , _
              "tblCurrentPric es", rstBatch!DirPat h + rstBatch!Filena me, True, rstBatch!Range
              ------
              where tblCurrentPrice s are linked to the front end app.
              Any fix to this?
              Reidar

                Comment

                • MMcCarthy
                  Recognized Expert MVP
                  • Aug 2006
                  • 14387
                  #5
                  Originally posted by Reidar
                  I got the same error (3349) when I try to import from Excel into a linked Access table.
                  -----
                  DoCmd.TransferS preadsheet acImport, , _
                  "tblCurrentPric es", rstBatch!DirPat h + rstBatch!Filena me, True, rstBatch!Range
                  ------
                  where tblCurrentPrice s are linked to the front end app.
                  Any fix to this?
                  Reidar
                  Link to the spreadsheet and append to the table.

                    Comment

                    Previous template Next
                    Working...