Access 2013 - Dbase (.dbf) Table Import option

This is old, but I found it in a search as I too have to support access to dbase for tabular data and GIS (shapefile) support.  Thanks for your honesty. I hope Microsoft includes in their research and valuation of support costs, the cost of losing customers to Linux. Not that it matters to you, but because of these very things, I have been researching just that. Zorin has been working well for me. GIS support was my last hold back from migrating away from Windows. Now QQGIS runs on Linux exactly as it does on Windows.  This is my last workstation/Windows. Not that Microsoft cares.

Enabling xbase/DBF support in Microsoft Office/Access 2013

Look, there are at least three ways to deal with this problem, and probably more. 

One is to continue to use the 2010 version of Access. It works as it always has. 

Another is to use the alternative method of importing the data into Excel first. That also continues to work.

And still another is to do something like Broggy69 did and create your own solution.

It's a PITA, but it's not the end of the world.

Our company's enterprise agreement makes it difficult to maintain Access 2010 support across new users as they receive PCs.  Using Access 2013 - how can I "Link" to a DBF file so I can adjust information but not break the file's relationship with the SHP and SHX in a GIS Format?  Broggy69's versions import a copy, they do not link.

Importing into Excel, converting to .xlsx and importing into Access will break this relationship with SHP/SHX.  So, yes, this is a PITA, because now my technicians need to learn how to do the types of scripting and data quality algorithms directly in ESRI and/or qGIS based products rather than the extremely simple yet powerful VBA options in Access.  We have to use ESRI based reporting mechanisms rather than the simple and powerful Access report designers.

Universal data accessibility is one of the great values in Microsoft Access.  Dropping DBF support really limits it as a tool for GIS data quality/analysis.

I guess it is not the end of the world for my business, we'll adapt.  But it does lead to the end of my relationship with Microsoft in using Microsoft Access for this line of work.

Wow. I just want to say thank to the user that marked my solution as abuse. I guess sharing code to help people import their dbf files is abusive. What a way to handle something you disagree with.

You just became worse then Linux and Apple users.

I am done with this forum.