File bloat !

Microsoft Project

    Sponsored Links

    Next

  • 1. copying dates from excel
    I am copying dates from excel into project and the dates arent copying accurately. i tried copying the finish dates first and that didnt work. fyi there some blanks for dates in the excel file
  • 2. How to print all predecessors to a given task?
    I would like to print all predecessors to a given task (and only them). How can this be done?
  • 3. Proj 2003. Optimally dividing work between assigned resources
    In regards to the following query. All the tasks are 'Fixed Units' and 'Effort Driven'. All resources have a 'Resource Availability' of 80% for the duration of the project. By default, when you assign a second resource to a task, Project will evenly redistribute the Work between the two resources e.g for 100 hours of work, it will assign 50 hours to each resource. Is there a way in Project of making the redistribution more 'intelligent'? For instance, it would be useful when 'Levelling' the Project if the Work was redistributed between the assigned resources optimally, rather than requiring each resource to do half the work. There are several tasks in my project where I have assigned 2 resources. I don't actually mind what percentage of the work is done by each resource - it is a case of whoever is free at that time. -- Project Manager Swordfish Studios Ltd
  • 4. Non/Near Critical Tasks
    Hi all, Sorry I haven't been around for a while but I have a problem that I know you guys are always good at solving. I want to be able to filter to show non-critical tasks that would affect the critical path if they slip within a certain criteria i.e. 2 days slack, 5 days slack, 10 days etc. Is that possible? I know I've never been too good at explaining exactly what I need but basically I want to report on tasks that could affect the critical path should they start to slip but sort of graded for severity. The single CP and 'critical' filter works well for worst case but I want 'near critical', 'only critical with pertracted delays' and 'not critical in any form'. Thanks in advance, AndyB
  • 5. choosing an early critical path
    I have a project where I ship to a customer in the middle of the project and would like to calculate the critical path for that ship date and not the end of the project. Is there a way to do this?

File bloat !

Postby Adrian » Sat, 30 Jun 2007 15:41:52 GMT

I recently purchased MS Project 2007.  I continually crash when trying to 
print large project files (300 line).  I watch the file being sent ot the 
printer and it grows to 25 MD sometimes.

Why is that.  When my partner prints the same file in MS Project 2003 it is 
about 800 KB.

Why so bloated in 2007?


RE: File bloat !

Postby SmltIEFrc2Vs » Thu, 05 Jul 2007 06:34:02 GMT

Although I cannot explain the bloat, here is what I tried to fix it when it 
happened to me:

1. Save the file as XML and then reopen it, save as a new file.
2. Save it to Project 2003 format, open it in 2003 and immediately save it 
as mpd file.  Then reopen the mpd file and save as.

I had better success with method 2, but I still ended up recreating the thing.
-- 
If this post was helpful, please consider rating it.

Jim
It''s software; it''s not allowed to win.

Visit  http://www.**--****.com/ 
about Microsoft Project







Similar Threads:

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

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

Such as:
-Is there a delete/define/restore or defrag utility available for MS Project 
files.
-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?
 

Regards.........Pratta

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

Geoff,
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 
graphics.

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 
Project"

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.
John
Project MVP

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

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

Anyone know of any workround ?

EG: would pictures stored as .WMF or .PNG have same problem ?

Chas.

5.Fixing Bloated files

Hi All,
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?

Dave 


6. Bloat

7. Bloated / Slow global.mpt

8. Token bloat



Return to Microsoft Project

 

Who is online

Users browsing this forum: No registered users and 10 guest