1.MS Project 2003 VBA "File Bloat"?
2.Treating File Bloat in Project 2007
MS Project: File Bloat Observations
We have had a problem with file bloat in 2007, that were not fixed by the
approaches in the FAQ doco.
We have done some research/ tried a few approaches, and the following
summarises our results.
We would be interested in comments. feedback.
General observations :
If a schedule is long enough, and with enough use, it will more than likely
become loatedi.e. larger in file size than is necessary to store all
the schedule data. Generally, it also seems to be more prone to crashes than
an ordinary schedule. When a substantial number of schedules are in use, file
bloat can pose a significant problem, because
-hard drive space is consumed unnecessarily
-bloated schedules crash more often than normal
-MS Project is slower when working with bloated schedules, and
-opening master files becomes slower and more crash prone
We have found that the best method to counter file bloat involves generating
.mpd files, which can only be done using MS Project 2003. Assuming there is a
copy of MS Project 2003 on hand, the method we use to nbloata schedule is:
-Open the bloated schedule in MS Project 2007
-Save the schedule as an MS Project 2003 file (using a different filename*)
-Open the bloated schedule in MS Project 2003
-Generate an MS Project database (.mpd) file from the schedule
-Open the .mpd file in MS Project 2007, and save the resulting schedule as a
new .mpp (do not overwrite another .mpp, the resulting schedule must be saved
as an entirely new file*)
* When saving a schedule by overwriting another .mpp, the resulting file
tends to be highly bloated, sometimes more than twice its original size.
Because of this, we suspect that when an overwrite is performed, MS Project
stores both the old, redundant from the file being overwritten, and the
current data in the schedule being saved, into the resultant .mpp file. As
such, when saving schedules for the purpose of nbloatingthem, it is
necessary to use unique filenames on each save.
Notes on conversion between MS Project 2007/2003/MPD formats
There were two things that were lost as a result of the conversions
between these formats:
-Names of exceptions in calendars e.g. ood Fridaybecomes nnamed
although the actual exception is still present in the calendar.
-Shading of cells in tables
This is because neither of these features were available in MS Project 2003.
However besides that, on inspection it appears none of the tasks, resources,
dates, custom fields, views, and settings, project labels (i.e. author,
manager, etc), customised calendars, task types or task constraints are
affected by the conversions between these formats. However, we did not
inspect financial settings, such as currencies or rates, because we do were
not using these features in the files we treated.
We would appreciate any comments/ additional info..
-Is there a delete/define/restore or defrag utility available for MS Project
-Is there a method to de-bloat files that does not require an older version
of the software to be loaded (requiring a separate machine)!
-Why isn't .mpd format creation included in 2007?
3.File 'Bloat' is becoming a showstopper
In article < XXXX@XXXXX.COM >,
Geoff < XXXX@XXXXX.COM > wrote:
> First post on this site from me.
> I'm using Project 2003 Standard and have a file that is c2500 lines and
> weighs in at about 31MB. I've been running monthly updates on copies of this
> for about 2 years now. After a heavy session of re-baseling this month I
> noted that the file had grown to about 91MB. This is a bit unmanageable.
> I trawled through other posts and found the "Project File Size is HUGE
> suddenly" post from December 2005 - sounded horribly similar to my
> predicament. The threads ended but I'm not sure that a solution was found.
> I've attempted the mpd save fix from FAQ 43 but without success - it wouldn't
> save on my machine because of insufficient virtual memory and I'll need to
> get admin help to increase this.
> I then reverted back to the pre re-baselining 31MB file and did a limited
> amount of re-baselining. I saved the resulting 33MB file to an mpd and the
> size of this surprised me at 276MB. I wasn't surprised therefore that the
> 91MB file was difficult to save as an mpd if that's the ratio of growth that
> Can anyone help me prevent this file size growth and/or point me at a
> utility to help me housekeep the 91MB file to make it smaller.
> The start of the project update cycle is approaching rapidly........
> Many thanks.
I'm assuming that by "c2500" you mean your file has 2500 tasks. A file
that size shouldn't even be 1M unless you have a whole lot of links or
First of all some advice. Are you doing a straight Save each time? If
so, that may be one reason the file keeps growing. I always use Save As
exclusively and I've never had a file bloat problem.
You still may need more memory to get this to work but here is another
method for getting the file size down.
1. Open a new blank file.
2. Go to Insert/Project and insert your bloated file.
3. Select the insertion point summary line of the subproject
4. Go to Project/Task Information/Advanced tab and uncheck the "link to
You should now have a cleaned up version of the file. Do a Save As,
close it and then take a look at how big it is.
Hope this helps.
4.A different file size bloat problem
A user of Project 2003, SP3 had a 1Mb .mpp file.
A few of the Views were updated via Page Setup to add logos into the
The pictures inserted were tiny .JPGs (about 10k)
New .mpp file size 8Mb, presumably because pictures stored internally
as BMPs (?).
The .mpp file will still zip down to 1Mb, but preference is not to
Anyone know of any workround ?
EG: would pictures stored as .WMF or .PNG have same problem ?
5.Fixing Bloated files
We recently experienced some 'bloating' of two published project files.
I've read the white paper on 'cleaning' bloated files. In our case
exporting the file to XML and re-opening it should solve it. However, I am
unclear about handing the server side of things. What are the step involved
when the file is published? Do I delete that server copy and replace it
with this new and improved file? Ifso, what happens to the previously
published assignments? Specifically will any of the users notice the
deletion and re-publication?
7. Bloated / Slow global.mpt
8. Token bloat