A family of Microsoft relational database management systems designed for ease of use.
Access 2013 - Dbase (.dbf) Table Import option
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.
158 additional answers
Sort by: Most helpful
-
Anonymous
2016-11-01T16:05:05+00:00 Actually...I'd rather it stayed open for a bit longer...maybe? Microsoft is still refusing to respond as to whether or not they will be issuing a patch or something for Access 2013 (which is technically the version being addressed by this thread). I know it's a previous version and all, but most enterprise level users are stuck with 2013 for the time...probably for another year or two. And, personally, I'm now stuck in the even more frustrating position of having to use "the one" version of Access which doesn't have dbf support. And no control over upgrade schedules...
Don't get me wrong...absolutely thrilled that MS brought it back...and is in the process of deploying the fix. I (and I'm assuming many in the GIS community) just need to know if there'll be a patch for 2013.
-
Anonymous
2016-11-01T15:52:20+00:00 As I started the thread I am happy for it to be closed, but don't see that I can close it.
Now I shall have to start one to get Pivot Tables restored (unless I have missed it being restored?) :-)
-
Anonymous
2016-11-01T15:15:53+00:00 I agree Scott. In Access 2016, I'm seeing they have brought back dbase in versions 3, 4 and 5 which is awesome!
This string should be closed to stop any further rants.
-
ScottGem 68,840 Reputation points Volunteer Moderator
2016-11-01T14:55:33+00:00 Umm Michael, before you start ranting and making yourself look foolish, you should read the whole thread.
In point of fact, the reason it was removed is because research showed it wasn't being used. But there was a significant group that required it and Microsoft has restored it!