ArcGIS should automatically record version of ArcGIS required to open LYR, MXD, or Layer package in the File properties.
Now it's impossible to understand which version was used to create LYR, MXD, MPK, LPK file, and which version is required to open.
This is what I was looking for back from my comment in 2013, so maybe by 2021 this might get implemented. But then again ArcGIS for Desktop mxds might be deprecated by then in favor or Pro anyway.
Still no response from ESRI. Unbelievable.
I put in an enhancement request several years ago on this one but it's gone nowhere. The use case we had for years is this. We have people who collaborate on MXDs but not all users are running the same version of ArcMap. It would be extremely helpful if ArcMap could be setup to save an MXD back to it's version so that the MXD can be modified by users running a newer version of ArcMap and not create an MXD that can't be opened by the author.
Where this really comes into play is when running a script to update SDE datasources on all MXDs recursively. I ran into an issue earlier this year when the script I had written was run using 10.4.1. A handful of our users are still at 10.2 but there was no way programmatically to determine that so I saved everything out at 10.4 version. That left MXDs at the wrong version for users of 10.2.
Randy, I hear ya, we operate in a multi-version environment and have for years. It blows me away how Esri actually changes the file format with each release, I can't think of another company that does that. Versions might change, but file formats typically span multiple software versions, at least for most companies.
Anyhow, moving on to an actual helpful comment, go check out arcgis 10.0 - Using ArcPy to determine ArcMap document version? - Geographic Information Systems Stack Exchange . Since Esri packages oletools with their ArcMap Python distributions, you should be able to run the code in the bottom response as is.
Unbelievable? For Esri, sadly, no. The saddest part of all is how simple something like this would be to implement. MXD files are just OLE files, which is the same nuts-and-bolts file format used by MS Word, Excel, and many others. See my response to Randy below for an example on getting information outside of Esri products.
This should simply be shown under the Map Document Properties - it's unbelievable that this was never added despite repeated calls for it over so many years.
Retrieving data ...