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: Newest
Most helpful Newest Oldest
  1. ScottGem 68,840 Reputation points Volunteer Moderator
    2016-02-17T18:11:58+00:00

    Recently, there was a thread here from someone complaining because he felt he was being forced to upgrade (from Access 97). Now we have people complaining they want to upgrade but can't because a feature, critical to them, was deprecated. My point is Microsoft is damned if they do and damned if they don't. 

    Don't get me wrong, I deplore dropping support for dbfs. In my opinion it's almost the same as dropping support for csv. But the way to fight back is through UserVoice.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-02-17T17:28:12+00:00

    The User Voice forum "vote" option is helpful.

    Keeping Office 2010 is fine as a temporary work around, but it certainly is far from a "best practice" to use outdated software and operating systems.  And they will eventually become impossible to acquire, use, and that isn't even considering the potential security risks after EOL.  So being "more fun to rant at Microsoft" is hardly the issue.

    Was this answer helpful?

    0 comments
  3. George Hepworth 23,120 Reputation points Volunteer Moderator
    2016-02-17T17:08:14+00:00

    Apparently you failed to read my post carefully. I didn't suggest reverting back to Access 2.0, did I? Only that a viable solution does exist if you care to implement it. Hyperbole is a tasty snack, but not a satisfying meal.

    KEEP Access 2010 IF THAT'S WHAT YOU NEED.

    Go, use the open item at the User Voice forum to express your support for this suggestion. It's there, the Access Team reads all of the suggestions.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-02-17T16:33:17+00:00

    Really???

    So, you will still be running Windows 1.0 and drive a Ford A ??

    Access 2010 has some serious flaws (like sorting errors, which, for me anyway, is a serious flaw for a DBMS) that I would like to have fixed by using a newer version. Actually I find it rather sensible to upgrade to new versions.  If I didn't, one could in truth say Microsoft has been wasting 6 odd years making new versions.

    Same company has a habit of rendering old version useless and without updates, when going back 2-3 versions.

    Many things in the Access 2016 are really nice and useful, but removing the most widely used standard import/export makes NO sense.

    AND, no, ODBC, ISAM or going via Excel (or anything else) is NOT a solution, when you do this many times every day and have functions built for this purpose in Access 2010.

    SO, no, the answer is not "simple" as you may think.  And, NO, I waste time "ranting" at MS.  But, MS clearly takes no interest what so ever in our problem, although it should be an easy fix from their side.  I guess customers don't matter so much anymore. 

    What happened to "We feel your Pain" MS?

    Was this answer helpful?

    0 comments