Access 2013 - Dbase (.dbf) Table Import option

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.

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.

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.

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%.