Access 2013 - Dbase (.dbf) Table Import option

Anonymous
2013-02-03T16:16:55+00:00

I need to be able to import read/write Dbase dbf tables - yes they are still around so why has the standard option that was in Access 2010 gone?

I have seen mention of ISAM, which is gobbledegook to me. So please a simple answer - what do I need to install or change and how do I do it?

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
ScottGem 68,840 Reputation points Volunteer Moderator
2016-09-08T09:08:22+00:00

Was this answer helpful?

60+ people found this answer helpful.
0 comments

158 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2013-02-09T22:52:17+00:00

    I was able to convert my dbf to an xml file, but Access 2013 365 did not successfully import it.  It seemed to start and then nothing, no error message.  Looks like it crashed.  ODBC is not an option for my situation.  I suspect I will stay with Office 2010 and not upgrade to a downgrade!

    Thanks for responding,

    J. Austin

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-02-10T09:23:07+00:00

    It seems many are missing the point.

    In Access 2010 there is a drop down option to import dBase files (External Data > More > dBase files option at bottom of list), which is what I need. In Access 2013 this option not longer there, but Access 2013 runs the 2010 dBase Database I created in Access 2010.  The problem is I cannot import more dBase tables. Utterly ridiculous!

    So come on Microsoft - why, when Access 2013 works with dBase tables, have you removed the import option? How about an update to Access 2013 restoring the option, or a very simple statement of how to achieve this without messing around with Registry entries or file edits. You made the mistake!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-02-11T04:26:02+00:00

    This is the right focus on the issue. It doesn't make sense to have battalions of users and vendors making indirect "solutions" to a problem Microsoft can fix so much more easily either by publishing a manual fix or better by putting this function back in the product they mistakenly crippled.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-02-19T16:53:40+00:00

    The silence from MS is deafening!

    For those of you who have committed to 2013 and don't have 2010 to fall back on, rather than using a 3rd Party vendor you can of course open your dbf tables in Excel and save in Excel Worksheet format, which can then be imported to Access 2013.

    I only regard this as a temporary solution if you don't have 2010 and not a cop out for MS, who should be pulling out the stops to fix this.

    Was this answer helpful?

    0 comments