Tag Info

New answers tagged


You could try using XTools Pro, which has an autosave MXD function built in


My understanding is that Background Geoprocessing runs as a separate process and, unlike Foreground Geoprocessing, is unaware of your current ArcMap environment. Consequently, I don't think you'll have success with your current approach. AutoSaving maps is not the same as AutoSaving edits but you could look at Incremental "auto save" in ArcMap ...


When you are running a script in the background, a python process is spawned that is separate from ArcMap. So essentially, arcpy.mapping.MapDocument("CURRENT") is attempting to open a map document that it cannot see. This makes sense as imagine the issues if you had multiple .mxd open: Python would not know which one you mean by "CURRENT". You can see this ...

Top 50 recent answers are included