Tag Info

Hot answers tagged

5

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 ...


3

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 ...


2

I would try the following: If you have v9.3 users trying view v10 map doc: Create v9.3 geodatabase and copy and paste features datasets/features classws in ArcCatolog from geodatabase 10 to 9.3 (have not tested this). Then resource your v10 mxd layers to v9.3 geodatabase data, and finally Save as Copy of v10 mxd to v9.3 mxd. Create layer package in v10 ...


1

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


1

As you noted there is no property to test for a thumbnail. In VBA you can test for the existence of a thumbnail with this simple bit of code: Public Sub test() Dim pMapDocument As IMapDocument Set pMapDocument = ThisDocument Dim pic As stdole.IPicture On Error GoTo eH Set pic = pMapDocument.Thumbnail Exit Sub eH: MsgBox "Map ...



Only top voted, non community-wiki answers of a minimum length are eligible