Access 2013 - Dbase (.dbf) Table Import option

People, get off the focus of government being the only users (I have a POS system that uses them) and Excel doesn't do everything that people need to do (such as delete, compact and re-save the file) that is required when working with the Dbase files.

In the mean time, I've had to find another piece of software that does the job.

I just wish they had left it so we could still use Access, because it fit my requirements.  Now I use Access less often than I did.  I'm left to believe that Microsoft wants us using Access less often, when they remove features people used!

Those government agencies still distributing their data in *.dbf format probably contracted out the creation of the distribution method >15 years ago. 

And probably have no plan or budget for replacing it.

And it will take years until this issue comes to "critical mass" for those agencies and the people who are required to utilize the data.

The wheels of government turn oh-so-slowly....

As hard as this is to believe, it is more expedient to get Microsoft to admit they made (yet another) error and to FIX IT!!!

SO while you may not be defending Microsoft; don't be surprised to see (folks like me) whining and complaining until Microsoft decides to FIX IT!!!

After all Microsoft doesn't engrave things in stone ... or even CEMENT  ( CE, ME, NT ... HA!!)

That's possibly a more productive way to proceed than posting complaints in a Q& A forum would be.

Keeping in mind that the same government agencies who are still distributing their data exclusively in .dbf format are not likely to be on the cutting edge as far as Office versions is concerned either, it may well be that a good number of them haven't noticed yet. That's speculation on my part, though.

In any event, directing problems to the appropriate MS sources should be more productive than posting complaints here. I'm not saying there's anything wrong with the latter, just that getting your message in front of the right people is going to be more effective.

And one more time, there is a viable alternative readily at hand, called Excel. You'll also need to explain why that doesn't meet the needs of many, if not most, organizations who need to import .dbf files.

And finally, I hope it doesn't sound like I'm defending MS here; I'm just trying to point out the realities of the current situation.

 

They need to FIX IT!

 

I wish you the best of luck in getting it done.  I hope they do.  I am not going to hold my breath on it though.