Best Practice for Updating Attribute Table then Populates into another Database

01-25-2018 02:05 PM
Occasional Contributor II


I was wondering what is the best practice for a project I am working on.

We have a feature that will always need updates as well as additions to it.  I need to also have an Access database for it.  The idea is to not update the feature within ArcMap (the attribute table) then open Access and update it in there as well.  We only want to do updates/additions once.

Do you have any suggestion for me on what to do?  My goal would be to update or add a feature in ArcMap then it populates in Access so that I only need to do this process once.

I've looked into it some, and it seems like this is not possible unless I use Excel?  I am not entirely sure though.

0 Kudos
0 Replies