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. George Hepworth 23,120 Reputation points Volunteer Moderator
    2016-02-17T19:11:58+00:00

    Because the leaders of the Access Development Team tell us they do?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-02-17T18:42:16+00:00

    Thanks Dad!  My inbox was filling up with these useless rants.

    P.S.  I've already taken the advice to put a vote in at User Voice, but is there any proof that Micro$oft actually listens to that?

    Was this answer helpful?

    0 comments
  3. George Hepworth 23,120 Reputation points Volunteer Moderator
    2016-02-17T18:28:59+00:00

    Okay, I'll bite, what do you need, exactly? What is it that you'd find in Access 2013 or 2016--other than the ability to link to the .dbf files, of course, that you find compelling?

    Unfortunately, this entire thread has been marred by  a whole lot of anger and sarcasm over what is really a fairly pragmatic question. Can you figure out how to use dbf files with Access in Access 2013/2016? The answer is "no". The next question is, what do you do about that? Shouting here has virtually no effect. Sarcasm has virtually no effect. Complaining here has virtually no effect.

    There is at least one perfectly viable way to do what you want (or need).  You refuse to consider it because it's not what you want: Use Access 2010 while working for a more acceptable solution.

    Go to the User Voice forum and vote up the suggestion there for restoring the ability to link to DBase files in newer versions of Access. Otherwise, I have to think that ranting and name calling here is the real point.

    I've been creating Access and Access/SQL Server solutions for clients for two decades. One thing I learned many, many years ago is that griping about what isn'tsolves very few problems. Name-calling solves no problems. Finding a way to craft a solution? Yeah, that works a lot of the time, in fact, pretty close to 100%.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-02-17T18:12:53+00:00

    Access 2010 is NOT what I NEED, BUT it is my only option, because MS fail to deliver what I NEED in the new versions!!!

    That you did not get my point says more than you AND MS imagine.

    Fortunately, many professionals (not just using MS apps for playing around) agree with what this topic is about.

    So, if if you don't understand, then please just find the gaming section ...or whatever, and stop wasting space here.

    Was this answer helpful?

    0 comments