nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Data Sources in Pro vs Map

DavidGray1

Hi Community; A question pertaining to importing mxd projects into a new Pro project. I have a very nice but older mxd map project (and all of its supporting files) that I am hoping to import into and create a Pro gdb project from. Following the instructions at

https://pro.arcgis.com/en/pro-app/3.2/get-started/migrate-existing-work.htm

I have found many of the data layers in the Layout Map Frame and the Map itself have broken data source file paths. What seems odd is that under Properties when looking at the Source, the file path is to an Access mdb. Now I have that mdb but it is not reading from it correctly? Frankly I didn't even know one could source and Access mdb for layer feature definitions. Now I also have the shapefiles for the corresponding layers and resetting the source path to them just fails. And Pro of course doesn't directly read from an mxd so that doesn't work either. Redefining the source is being elusive.

Any thoughts or ideas on this?

Thanks;

Dave

Trouver plus de publications taguées avec

Accepted answers

All comments

Luke_Pinner

If those Access DBs are personal geodatabases, you'll need to convert them to a file geodatabase or other supported format andthen repair the datasources to point to the new feature classes.

From your "Migrate existing work" link:

Note:
Personal geodatabases (.mdb) are not supported in ArcGIS Pro.

And from the ArcGIS Pro -> ArcMap FAQ:

Can I use personal geodatabases (.mdb) as data sources for ArcGIS Pro?
Personal geodatabases are not supported in ArcGIS Pro. However, in ArcMap you can run a geoprocessing tool to convert personal geodatabases to file geodatabases. Alternatively, in ArcGIS Pro you can make an OLE DB connection to a personal geodatabase. This gives you a read-only view of the data and allows you to import the data into a supported geodatabase.

DavidGray1

Thanks Luke; This will take some investigation tomorrow. But it sounds like there are solutions to the issue. In this case the access database is an mdb which I guess is a personal database. This will get interesting I am sure. Thanks again!Dave

BarryNorthey

Personal geodatabase feature classes can be easily converted to fGDB format using ArcGIS Desktop if you still have it. If not, the Pro - Data Interoperability extension or QGIS can do the conversions.

danielri

Two possible issues, (1) Personal geodatabases are not supported in ArcGIS Pro and (2) Access databases are depreciated. Ensure you have the Access Database Engine (64-bit) Office 2016 drivers loaded on your computer.

see: Download Microsoft Access Database Engine 2016 Redistributable from Official Microsoft Download Center

JohnGuilfoyle

Pro uses File Geodatabases.
You should Export Features to a new or existing File Geodatabase and then
change the Source.

DavidGray1

Thanks John; A wise precautionary recommendation. I am glad that I have been distracted from trying some of the OLE DB possibilities over the weekend. Seemingly rude at times, sometimes it pays to see what additional input come in. Thanks again. Dave

DavidGray1

Hi Richard; Looking at the link, I see that the process - or at least the explanation of it - can get complicated in a hurry. I have Access through MS 365 which had the latest annual fee paid for last October and presumably is updating with releases and patches etc on an on-going basis. Is there away to query and find out if what you are linking to with Engine 2016 Redistributable is present and installed? Thanks; Dave

danielri

Outlook 365 does not have the required drivers for ArcGIS Desktop (a.k.a., ArcMap) or ArcGIS Pro to direct to connect to a .mdb database. The Office 2016 drivers are required -this also enables Excel spreadsheets .xls and .xlsx. access. Since you have ArcMap and ArcGIS Pro I would install both the 32 bit and 64 bit drivers. These can also be found on the my.esri.com/downloads pages if you have a my.esri.com account with download permissions.

DavidGray1

Hello Luke and others that replied to this inquiry. First I apologize for taking so long to get into and try some of the suggestions made. Suffice it to say I got called away on business travel and then proceeded to catch the grunge and get sick. Enough said.

So, I have pursued the suggestions and have successfully made an OLE DB connection to the older .mdb personal database. Test connection successful. In proceeding on to working with the connected data with the connection made in ArcGIS Pro, I have run into some issues. When I attempt to import a table of what I surmise will become a feature layer in Pro, I only get an export option and not an import option when right clicking on the connection listed in catalog. I do notice that the connection is listed as a .odc file. The example in the excellent Bridging Data article you recommended then has the import table example connecting to a .gdb listing underneath the .odc listing. Am I missing a step here?

As ever, thanks for any input on this bit of a convoluted process. Dave

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.