Arcgis watergems compatgibility3/31/2024 ![]() Currently the person creating the map is responsible for saving old versions of mxd files for any clients that do not have an upgraded version of ArcGIS. I think ESRI should change the responsibility to translate mxd files from the map publisher to the client. There is no statement (that I can see) stating this in the v10.3 documentation. When a new release of the software is available, I think there should be a HUGE disclaimer stating something like NOT BACKWARDS COMPATIBLE! so we would know to copy them down to the previous version. Our workflow has been compromised because this wasn't realized until 100's of maps had been saved at 10.3 and our 10.2 users can't open them. Ideally, every forward version of the software should be able to identify which version the user is running and open the map. Why hasn't this feature continued in the software? At the very least, we should have an option to "save as" the version most used in our workflow. Now, as a couple users upgrade to v10.3, we find the backward/forward compatibility of our mxd's lost. The backward/forward compatibility with 10.1 and 10.2 saved time in our workflow. Previously, we would have to save a copy down to the previous version if we had users still running a previous version. The release of v10.2 allowed the capability to save an mxd and a user running v10.1 could open the map without an error message.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |