none
Error 3310 - This property is not supported for external data sources or for databases created with a previous version of Microsoft Jet. RRS feed

  • Question

  • I am building an Access 2010 application which loads log files from automated IC programming machines, using the "DoCmd.TransferText acImportFixed command once a minute.  The app is mostly pretty solid, however after ~11,000 records imported, the DoCmd.TransferText fails with a 3310 error.  If I shut down the app and restart it, it works fine for another 11,000 records or so.

    A search on the internet for this error indicates it is a problem going back for some time, I found reports of similar behavior in Access going back to 2004.  Error 3310 (Access 2002/Win XP)

    Is this a known problem?  Are there fixes?

    Friday, March 18, 2016 5:04 PM

Answers

  • If you're working with fixed width text files or even delimited text files you are probably better off using plain old VBA file i/o commands or the newer FilestreamObject and TextStream objects to open, read, and close the files yourself.  Use whichever mechanism you prefer to open the file and read individual records. Parse them with VBA string functions, and use recordsets or SQL to bring them into your tables.

    -Bruce

    • Marked as answer by MJ McBride Thursday, March 24, 2016 3:49 PM
    Friday, March 18, 2016 8:59 PM

All replies

  • In the link you included, part of the solution mentioned was to add a line of code; DoEvents

    This should give the engine a break to complete the last transfer before the next one starts


    Just takes a click to give thanks for a helpful post or answer.
    Please vote “Helpful” or Mark as “Answer” as appropriate.
    Chris Ward
    Microsoft Community Contributor 2012

    Friday, March 18, 2016 6:31 PM
  • If you're working with fixed width text files or even delimited text files you are probably better off using plain old VBA file i/o commands or the newer FilestreamObject and TextStream objects to open, read, and close the files yourself.  Use whichever mechanism you prefer to open the file and read individual records. Parse them with VBA string functions, and use recordsets or SQL to bring them into your tables.

    -Bruce

    • Marked as answer by MJ McBride Thursday, March 24, 2016 3:49 PM
    Friday, March 18, 2016 8:59 PM
  • The DoEvents did not help the problem.  I added the command in several locations in my import routines with no luck.  I am going to follow Bruce Hulsey's advice and go the plain file i/o route.

    Comment to Microsoft, you have a bug in your DoCmd.TransferText routine which has been reported in help forumns, at least according to Google searches for a dozen years.  My experience matches reports I saw from others, the command fails after about 10-12000 calls.

    Monday, March 21, 2016 4:19 PM
  • Thanks for the suggestion Bruce, it looks like using basic VBA file i/o is the way to go.
    Monday, March 21, 2016 4:21 PM
  • Hi MJ,

    >> it looks like using basic VBA file i/o is the way to go.

    If your issue has been resolved, I would suggest you mark the helpful reply as answer to close this thread.

    In addition, for bug issues, I would suggest you submit a feedback in the link below:
    http://access.uservoice.com/

    Best Regards,

    Edward


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Thursday, March 24, 2016 8:39 AM