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 No 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 No comments

158 additional answers

Sort by: Most helpful
  1. Tom van Stiphout 40,216 Reputation points MVP Volunteer Moderator
    2014-10-10T03:27:19+00:00

    > You still haven't shown how that is illegal, or what laws are broken by copying a file from one computer to another.

    You didn't really think that your POV would fly, did you?

    Check this out: http://www.microsoft.com/en-us/download/details.aspx?id=13653

    Section 1.d of the Office 2010 EULA:

    d. Separation of Components. The components of the software are licensed as a single unit. You may not separate the components and install them on different devices.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-10-09T18:47:01+00:00

    No, you don't need Access 2010 installed to make this work. I have a fresh install of Windows 8 and Office 2013 64 bit, and the method works.

    If it is a short term problem, you can still use VB code to import the DBF files into access and use them as you need.

    It is quick, and would help you get off of dbf files.

    You can also use my code to put the DBF files in an sql server, if you don't want to use access. After some modicifcations.

    -Glenn

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-10-09T18:43:58+00:00

    I understand what you are saying, and I have a fresh install with windows and a fresh install of Office 2013, and the method works. Again 100% 64 bit install. So I have actual working proof of this.

    Using an older .Dll no matter where you get it from is not illegal. You still haven't shown how that is illegal, or what laws are broken by copying a file from one computer to another.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-10-09T17:03:31+00:00

    Yes, ultimately Broggy's solution does not solve the problem in the future, which is Microsoft Access 2013's lack of native support for the DBF files.  For Broggy's solution to work, one still needs to install Access 2010, at which point you may as well continue to develop your applications in Access 2010.

    My short term solution to this problem has been to have Access 2010 installed on team member's who need to use .DBF files, this has been worked out with our enterprise agreement.  My long term solution is to not use Microsoft Access in the future.  That will be painful, but in the long run I think it'll be for the better.

    Was this answer helpful?

    0 comments No comments