Project files corrupted in 2007 when saving as 2003

[juliangall]

I have had problems consitently when I make changes to a project in Project
2007 and save it in Project 2003 format. These usually manifest themselves as
a circular reference warning when I open the file the next day. Sometimes,
there is no message but the task row identifiers are out of sequence. I have
also just had a colleague have similar problems. He is also using 2007 to
work on files in 2003 format. I haven't yet tried to create a repeatable set
of steps to reproduce this. Has anyone else had this problem? I've found a
couple of comments by Googling "microsoft project 2007 save as 2003
corruption" but nothing conclusive.

Thanks,

Julian

 

[JulieS]

Hello Julian,

I can confirm that there have been a number of reports in this newsgroup
as well as on the connect site for Project 2007
(https://connect.microsoft.com/feedback/default.aspx?SiteID=235) with
issues about using Project 2007 to save files in Project 2003 version.

Some of the items which are consistent in the reports of errors are
password protected files, as well as project files with blank lines in
them. I also suggest making sure you do not have any links on summary
tasks as this is a long standing avenue to circular reference errors.

Is it possible to working solely in Project 2007? Is it possible for
you to install 2003 instead of 2007?

I hope this helps. Let us know how you get along.

Julie
Project MVP

Visit http://project.mvps.org/ for the FAQs and additional information
about Microsoft Project

 

[juliangall]

I have been warned about having blank lines but I do have links on summary
tasks. I have re-installed Project 2003 until all my colleagues are able to
use 2007. If links on summary tasks are a long-standing problem, it's a shame
it hasn't been fixed yet.

Thanks for your reply.

Julian

 

[JulieS]

You're welcome Julian and thanks for the feedback.

Julie

 

[juliangall]

I see SP1 for Project 2007 acknowledges this bug and says it's fixed. Let's
hope so!

See http://support.microsoft.com/kb/942386

I do think it's very poor that the first acknowledgement of a problem is
when the fix is delivered. Microsoft have obviously known about it for long
enough to correct it.

Julian

 

[liquidray]

The same thing happened to me this weekend.
I worked on a massive project plan all weekend and when I reopened my
project plan Project complained of circular dependencies that were not there
before.
I cant believe that they would release a product with a feature that
completely corrupts your work.

 

[juliangall]

Even with SP1, I have had problems with saving in 2003 format. It's not so
bad as before but I'm not prepared to take the risk. I work on project plans
in 2007 format now and convert them at the last minute to send to colleagues
who only have 2003.

I don't suppose Microsoft will ever fix this issue as they want everyone to
upgrade.

Julian

 

[clk81]

I'm having major issues with this as well with using 2003 files in 2007.
I've noticed that the blank lines aren't new tasks but rather my old ones
being shifted around. I end up finding them in random places later on in my
project which really, really messes things up and some times takes hours to
fix.

I'm willing to downgrade my Project version to 2003, but do you think that
my collegues that open and view the project plan (usually through sharepoint)
will cause it to be corrupted again?

Thanks! I'm glad I'm not the only one!