file sizes

[Roger Rice]

I work with about 40 separate schedule files and notice that the file sizes range from 300K to 8M (and any size in between). All of the schedules are the same, i.e., modeled from one standard template and modified only in schedule dates. Furthermore, they each seem to function the same programmatically.

Question: How can I condense the larger files to a more reasonable size? This is an extremely urgent problem as this affects storage requirements when saving the live files as well as archiving files.

Question: What is the reason/explanation for these growing so much in size?

 

[Gary L. Chefetz [MVP]]

Roger:

See the following MVP FAQ for details on a therapeutic strategy:

http://www.mvps.org/project/faqs.htm#File Bloat - Might be Corruption

I work with about 40 separate schedule files and notice that the file

sizes range from 300K to 8M (and any size in between). All of the schedules
are the same, i.e., modeled from one standard template and modified only in
schedule dates. Furthermore, they each seem to function the same
programmatically.

Question: How can I condense the larger files to a more reasonable size?

This is an extremely urgent problem as this affects storage requirements
when saving the live files as well as archiving files.

Question: What is the reason/explanation for these growing so much in

size?

 

[Gérard Ducouret]

Hello Roger,

Have a look at the FAQ #43 :File bloat
http://www.mvps.org/project/faqs.htm

Gérard Ducouret

I work with about 40 separate schedule files and notice that the file

sizes range from 300K to 8M (and any size in between). All of the schedules
are the same, i.e., modeled from one standard template and modified only in
schedule dates. Furthermore, they each seem to function the same
programmatically.

Question: How can I condense the larger files to a more reasonable size?

This is an extremely urgent problem as this affects storage requirements
when saving the live files as well as archiving files.

Question: What is the reason/explanation for these growing so much in

size?

 

[Roger Rice]

Gary

I've tried this and it doesn't seem to work. It only reduced one file size from 2,609kb to 2,577kb; not much of a savings. Additionally, another file I tried this on actually grew in size. I really don't think the files are corrupted, just huge, i.e., 2,577kb versus about 300kb of the original file it was created from. All the files are active and seem to function programmatically OK

Help! Any other suggestions

Thanks much
Roge

----- Gary L. Chefetz [MVP] wrote: ----

Roger

See the following MVP FAQ for details on a therapeutic strategy

http://www.mvps.org/project/faqs.htm#File Bloat - Might be Corruptio

--

Gary Chefetz [MVP
http://www.msprojectexperts.co
We wrote the book on Project Serve

I work with about 40 separate schedule files and notice that the fil

sizes range from 300K to 8M (and any size in between). All of the schedule
are the same, i.e., modeled from one standard template and modified only i
schedule dates. Furthermore, they each seem to function the sam
programmaticallyThis is an extremely urgent problem as this affects storage requirement
when saving the live files as well as archiving filessize?

 

[Roger Rice]

Gérard,

I've tried this and it doesn't seem to work. It only reduced one file size from 2,609kb to 2,577kb; not much of a savings. Additionally, another file I tried this on actually grew in size. I really don't think the files are corrupted, just huge, i.e., 2,577kb versus about 300kb of the original file it was created from. All the files are active and seem to function programmatically OK.

Help! Any other suggestions?

Thanks much,
Roger


----- Gérard Ducouret wrote: -----

Hello Roger,

Have a look at the FAQ #43 :File bloat
http://www.mvps.org/project/faqs.htm

Gérard Ducouret

I work with about 40 separate schedule files and notice that the file

sizes range from 300K to 8M (and any size in between). All of the schedules
are the same, i.e., modeled from one standard template and modified only in
schedule dates. Furthermore, they each seem to function the same
programmatically.This is an extremely urgent problem as this affects storage requirements
when saving the live files as well as archiving files.size?

 

[Gary L. Chefetz [MVP]]

Roger:

You can always try rebuilding the plan by copying the tasks and resources
into a new plan and see if that makes a difference.

Gérard,

I've tried this and it doesn't seem to work. It only reduced one file

size from 2,609kb to 2,577kb; not much of a savings. Additionally, another
file I tried this on actually grew in size. I really don't think the files
are corrupted, just huge, i.e., 2,577kb versus about 300kb of the original
file it was created from. All the files are active and seem to function
programmatically OK.