Access 2013 - Dbase (.dbf) Table Import option

They would actually rather have dumped Access long time ago.  

User voice is, as far as I can see, just a container.

Sorry for all of us.

There have been rumors like that for decades. It wasn't true then and its not true now. I have been involved with people who have been part of the Access dev team for the last 10 years. I'm not going say there haven't been issues, especially between Access 2010 and 2016, but I can say that the people who manage Office have never wanted to "dump" Access.

I don't know what you are looking at but you clearly can't see very far. Uservoice is paid attention to. It will help to promote it, not tear it down.

I'm sorry for you. I don't know what your agenda is, but if you want Access to improve and affect changes, it certainly doesn't help to put up posts like you did. Posts that have no factual basis and just promote gloom and doom.

I am afraid, what you have experienced, is the MS "wall to keep users out of their way" technique.

They don't care.  They would actually rather have dumped Access long time ago.  Shows clearly when looking at what has happened with Access till now.  Degrading is their biggest "achievement".

Guess the only possible way is to stay with 2010 like some old guy (like myself) in here said, that also has given up hope.

User voice is, as far as I can see, just a container.

Sorry for all of us.

It seems this thread has gotten back on track, so I'd just like to encourage everyone to please vote on the uservoice website (see below).  I've spent the last two weeks corresponding cordially with some helpful tech folks at Microsoft...but can't seem to get it through to the folks that can do something about the problem.

Long story short, dbf is a core component of all GIS shapefiles.  And linking directly with GIS data tables in Access really is a necessity.  And I mean "on the fly" without registry hacks and without holding on to the pre-2013 versions.  Developers seldom have full control over the software upgrade schedules of all their clients.

So please, vote on the uservoice website...maybe if we get that number high enough, with enough honest & sincere comments, they will address the problem.

To Vote, Click This Link:

https://access.uservoice.com/forums/319956-access-desktop/suggestions/11075742-bring-back-the-support-for-connecting-to-dbase

This should bring you to the “Bring back the support for connecting to dBase” suggestion (Under “External Data Connectivity”…in the Access Suggestion Box). 

Click the “Vote” button

Enter your email address

Enter your name (the “Name” box will appear after entering your email address)

Click “3 Votes” (Or 1 Or 2)

Post a comment if you want!

Done

In reply to somebody's Reply:

The answer, of course, is very simple. You do NOT have to upgrade Office, unless you really want to. Or, of course, you can upgrade everything but Access.

That's one very viable solution that seems not to be welcomed because it's more fun to rant against Microsoft.

Upgrade to Office 20XX Standard for Word, Excel, et al. And keep Access 2010. Done.

Sorry but I never upgraded my Office (this is my first one). I just tried to work with other people that use dbf, and I can't. The answer for me was rather simple... I noticed that I had to Downgrade if I ever wanted to work with these people.

I know there are reasons not to work with dbf, but what if you followed rule number one?:

The customer is always right.

And you make a little tool that shows you are trying to help people even if they want to do something "easy" and unprofessional... Or make  a Youtube video telling us why you can't do it and what your recommendations are and study the different problems PEOPLE are having... and show that even though you want us to be professional (and your customers)... or will you only focus on those that were already born Prof.

It's a one hour job... much easier than replying to hundred posts.