This content has been marked as final. Show 8 replies
You could try using "save as" and just overwriting the existing mxd file name. That has solved mxd bloat (where the mxd just grows and grows) for me in 9.xxx.
Thanks Matt. It's just unfortunate there's no explanation behind it. Time to band-aid another ArcGIS 10 issue. I'll give it a shot.
I had a problem similar to this back in 9.2 and it came back when I installed Arc 10. Try changing your Geoprocessing option for keeping results to 'Never save' (or at least quite a bit shorter than the default of 2 months), clear the results, then resave the mxd. This fixed the problem for me. Hope this helps...
Btw, when I said resave the mxd, I meant to save it as a new mxd (save as)....
Did you ever get a fix for this? I am having a similar issue. My MXD grew to 48 MB. When I did the "Save As" trick, it only went down to 24 MB.
Before ArcGIS 10, my MXDs were never larger than about 1.5 MB.
Just changed the Geoproc save to "Never" and file size is now down to normal.
MXD files are just OLE structured storage. If you want to see what is in them there are a number of tools which allow you to do this.
I think that Visual Studio 6.0 has the dfview utility. I have also seen similar utilities written by others.
I have tried this and Save As... and Replace Existing-Yes, isn't working. I changed a feature color and closed a table just to have a visual. I have tried this several times in a row and it is not working.
There is another last-ditch effort you can do: open your bloated project, open a new, blank project, and drag your layers from the old to the blank, then save the new project. You will lose some formatting from the original document (e.g., extent), but there are times when the tradeoff for using this drastic measure will give you astonishingly wonderful results in space savings and performance enhancement.
Yes, it is very different from the "save as" method (which works well, up to a point).