S
Stuart Summerville
Hi all,
I'm after a method by which I can optimise the space used by MPD files
with MSP.
Having run various MPP files for some time, that only ever grew to a few
MB, I'm rather annoyed that these same projects converted to MPD files a
few months ago have now reached as high as 24MB.
Saving such an MPD as a new file sees it back to ~ 3MB so obviously the
inefficiency is fairly extreme.
Saving as a new file is no good as we have external systems that then
see the contents as a whole new project (some indexes or internal ID's
must be re-initialised in the process).
I've read on this ng that loading the MPD into MS Access allows one to
do a DB compress operation - indeed this does seem to work, but I'm
rather nervous as to any repercussions of this method.
I've had google sessions on several occasions trying to find SOME MPD
maintenance info out there, but sofar no luck.
Any tips?
Stu.
I'm after a method by which I can optimise the space used by MPD files
with MSP.
Having run various MPP files for some time, that only ever grew to a few
MB, I'm rather annoyed that these same projects converted to MPD files a
few months ago have now reached as high as 24MB.
Saving such an MPD as a new file sees it back to ~ 3MB so obviously the
inefficiency is fairly extreme.
Saving as a new file is no good as we have external systems that then
see the contents as a whole new project (some indexes or internal ID's
must be re-initialised in the process).
I've read on this ng that loading the MPD into MS Access allows one to
do a DB compress operation - indeed this does seem to work, but I'm
rather nervous as to any repercussions of this method.
I've had google sessions on several occasions trying to find SOME MPD
maintenance info out there, but sofar no luck.
Any tips?
Stu.