file keeps corrupting

[maryj]

Client was using Project 2003 SP-1/Win2K. She got a new PC with WinXP and the
same version of Project. As soon as tried to open her Project file - message:
Project has encountered an error. Ran repair on Project. She had the file
restored, worked on it for awhile and now it has become corrupted again. The
file has many , over 200 other subprojects linked to it. The other
subprojects range anywhere from 5 - 60 tasks. It has a shared resource pool.
There are also many macros in the main project file. Any idea if SP2 would
help resolve any of these issues? Any other suggestions.

 

[John]

Client was using Project 2003 SP-1/Win2K. She got a new PC with WinXP and the
same version of Project. As soon as tried to open her Project file - message:
Project has encountered an error. Ran repair on Project. She had the file
restored, worked on it for awhile and now it has become corrupted again. The
file has many , over 200 other subprojects linked to it. The other
subprojects range anywhere from 5 - 60 tasks. It has a shared resource pool.
There are also many macros in the main project file. Any idea if SP2 would
help resolve any of these issues? Any other suggestions.

maryj,
Massive linking between files (as in a master with many inserted
subprojects) is always a potential for corruption. One of the main
problems is when the files are moved around (i.e. the path changes).
That can cause links to "get confused". And remember, the resource pool
is also a linked file.

Just an observation but a subproject with only 5 tasks doesn't sound
like much of a subproject. Even 60 tasks is a small file. You might
consider combining some of the small subprojects into larger files (a
couple hundred tasks is a reasonable workable size). Combining some
files will help cut down the number of links and lessen the possibility
of corruption.

You also mentioned that a repair was run on Project. However I suspect
the problem is not with Project so much as it is with the files. Go to
our MVP website at: http://www.mvps.org/project/faqs.htm
and take a look at FAQ 43 - File Bloat? Might be corruption.

I wouldn't expect macros to cause problems but then again, it depends on
what they do. If they are mostly simple macros that set up custom views
or similar I don't see a problem. On the other hand, if they are complex
macros that re-configure file structure, then yes, they could be suspect.

Finally I don't know if SP2 will help but you can certainly try it. You
might want read about those issues fixed by SP2 on the MS website before
you install it.

John
Project MVP

 

[Rod Gill]

I agree: over-write, move or rename any of the 200 subprojects and a
corruption will occur sooner or later. You need all your PM's to have an
iron discipline with that many links.

Solutions are:
Project Server
Other companion tool
A VBA macro that temporarily consolidates or creates reports automatically.

I doubt 200 linked files is workable.

 

[maryj]

Thank you John and Rod. I passed along your comments to my client and here
are some additional comments from them.
"We have been working with the Master plan for several months without issue.
We also break the subplans down into two other "Master Plans" with only the
subplans that relate to each area. We can open the plan without incident on
this. The problem did not occur until we were given our new desktops with
what appears to be a new MS Project version on Thursday. The macros,
although complex, only dump data from project to reports in Excel. They do
not manipulate data within MS Project."
I don't belive they actually have a different version of Project - but they
now have WinXP rather than Win2K.
Thanks for any other insight you may have.

 

[John]

Thank you John and Rod. I passed along your comments to my client and here
are some additional comments from them.
"We have been working with the Master plan for several months without issue.
We also break the subplans down into two other "Master Plans" with only the
subplans that relate to each area. We can open the plan without incident on
this. The problem did not occur until we were given our new desktops with
what appears to be a new MS Project version on Thursday. The macros,
although complex, only dump data from project to reports in Excel. They do
not manipulate data within MS Project."
I don't belive they actually have a different version of Project - but they
now have WinXP rather than Win2K.
Thanks for any other insight you may have.

maryj,
First of all, you're welcome.

It is possible that the "new" version of Project was simply 2003 versus
2002 or maybe 2003 pro in place of 2003 standard. Nonetheless, neither
an updated version of Project nor switching from Windows 2K to Windows
XP should affect linking. Rather, as Rod and I both stated, the sheer
quantity of linked files is most likely what "did them in". With that
many links and without extremely diligent and disciplined users, it is
basically a matter of time before corruption creeps in. It looks like
they are at that point and jockying the files to new desktop PCs didn't
help.

My suggestion still holds - combine files to achieve a more reasonable
number of links. A master can always be filtered and/or sorted to
display selected information. Filters are a whole lot more robust than
links.

John
Project MVP