I suggest you ...

Bring back the support for connecting to dBASE.

Access has always been about connecting to other data sources. Excel can still connect to dBASE files, but support for Access to connect was dropped. You can see from all the chatter, that there really is a lot of people that still use dBASE files for data transfer.

Thanks again everyone for voting and for letting us know what’s your top priority.
We are listening to our customers and your feedback is valuable!
With that – dBase support is on our radar and is on our planned roadmap :-)

When will this be rolled out to enterprise Access 2016 clients? I have had to keep an old box running in order to run legacy databases. I have Access 2010 on Windows 10 Anniversary Update on my primary computer and it keeps corrupting the dbase files (this didn't happen on Windows 10 pre-AU).

Why is this being statused as Done! when it's only partially been done for a subset of Access users? The post makes it sound like it's been released for all Access versions but you have to read 4 paragraphs into the blog your link points to to find that it's only for 365 users. What are we supposed to do with the shiny new Access 2016 program we just installed?

I understand it's on the radar...but will it require a new "upgrade" of office? If so, will we potentially lose any other mission critical functionality?

As a future suggestion, when you compare all the new features of a release in comparison to the incumbent release, you may also want to indicate what will be missing and when/if those particular features will be available. If, as your project board members believe, the features are unimportant to the majority of the masses you would have sold slightly fewer copies but kept MS loyalty and respect of both new and existing users.

I may also remind MS that many small/medium size government agencies are heavily reliant on 'antiquated' data structures. The government is ALWAYS slow to modernize (sometimes by decades). I still have Access 2010 on my government machines with no plans to upgrade and I won't recommend them to if it will break a single mission critical system.

Trying to process national fire response statistics from the National Fire Incident Reporting System. Seems like all that data is collected in .dbf files from fire departments all over the country. This is a major issue if we cant read the data anymore. Any conversion suggestions Microsoft?