How can a MXD point to a path that does not exist?

Question

We work on ArcMap 10.6, and have MXDs using database connections (.sde files) that point to the C: of a user that no longer exists (e.g. C:usersalphatest.sde) and certainly, that path doesn’t exist on the PC from which the MXD is being loaded, but the MXD loads without error.
We were playing with connection neutral SD files for publishing, with the original MXD pointing to our development database. However, when we publish to our Pre-Production environment, it is still pointing to the Development environment despite no data store existing on the server for that connection. I would expect that publishing to fail or throw an error but it worked fine, how is this possible?

nr_aus · Answer

Ok im using 10.3, so there might be some differences here.
When you create a new Database Connection - the sde file itself is saved in AppData folder by default.
When you right click > Properties on the Connection in ArcMap, the 'Name' of the connection is by default set to where the SDE file is saved (which in my opinion is a bit rubbish).
The MXD does not save the connection references that appear in your Catalog view. These are stored in AppData folders.
HOWEVER.
If you have a layer in the MXD from the database to which your SDE file is pointing to -  and you open the MXD without having the connection file in your project or the connection configured, the layer still works. This suggests that the connection settings are saved in the MXD, but NOT the SDE file.
This makes sense, because you can save a .lyr file which points to a layer in a database, and not have the .SDE configured in your project.
When publishing, the MXD and publishing tools will probably use what is configured in the lyr file, (or just the layer).
Conclusion - Check the layers and their configuration properties. If they are wrong, update them accordingly and see what happens.

How can a MXD point to a path that does not exist?

One Answer

Add your own answers!

Ask a Question