Project 200 v 2003 compatibility

[DavidC]

Hi,

Looking for some guidance as to what the possible cause of a problem I nad
my colleague is having with Project 2003 amending and saving a file created
in Project 2000.

The sequence seems to be as follows:

1 A project file is created in Project 2000.
2 The file is then opened in Project 2003 and amended or progress is added.
3 We then try to save the file, or use 'save as'.

At this stage an error message comes up stating that the format is wrong and
we should save as an MPX? Irrespective of the file the message tells us to
save in, the only solution is to close without saving (hence loose all the
changes and progress).

The way arround seems to be to save the file before making changes as a
Project 2003 file then make the changes.

I came across this problem some months ago after buying 2003, and my
solution has been to revert back to Project 2000.

Has anyone else found this problem and is there a 'fix'? Both myself and my
colleague have the lastest update for 2003 installed. I though have reverted
back to using Project 2000 and resist using 2003 because of this issue,
especially since our clients often still have 2000 only.

Thanks for any thoughts.

Regards

DavidC

 

[John]

Hi,

Looking for some guidance as to what the possible cause of a problem I nad
my colleague is having with Project 2003 amending and saving a file created
in Project 2000.

The sequence seems to be as follows:

1 A project file is created in Project 2000.
2 The file is then opened in Project 2003 and amended or progress is added.
3 We then try to save the file, or use 'save as'.

At this stage an error message comes up stating that the format is wrong and
we should save as an MPX? Irrespective of the file the message tells us to
save in, the only solution is to close without saving (hence loose all the
changes and progress).

The way arround seems to be to save the file before making changes as a
Project 2003 file then make the changes.

I came across this problem some months ago after buying 2003, and my
solution has been to revert back to Project 2000.

Has anyone else found this problem and is there a 'fix'? Both myself and my
colleague have the lastest update for 2003 installed. I though have reverted
back to using Project 2000 and resist using 2003 because of this issue,
especially since our clients often still have 2000 only.

Thanks for any thoughts.

Regards

DavidC

David,
That sounds pretty weird. Project 2000 through 2003 are "fully"
compatible except for features and fields that were added with later
versions. However, if all you are doing is updating progress, variances
in functionality should not matter.

Can you open the Project 2000 file in Project 2003 and then save (i.e.
no changes) without getting the error message? If so, I might suspect
some problem with the changes you are making and we should examine that
process in more detail. However, if a simple open and save also gives
the error message then I suggest you run Detect and Repair.

Also, does this problem occur will any file? Does it always occur or is
it intermittent?

John
Project MVP

 

[DavidC]

John,
Thanks for your reply.

Certainly is a head scratcher. we can open a Project 2000 file and save it
as a Project 2003 file. That is how we have got arround the problem. Having
made the save it allows us to make changes and update without any issues.

I recall last year having exactly the same problem with a Project 2000 file
that I opened on the clients machine using 2002 making changes and not being
able to save them, consequently loosing all the changes.

Another thought has crossed my mind that I will try. It seems that it
'fails' once and then doesn't happen again, ie it is non reproduceable. The
effect is almost like 'seeding'. Once the 2003 programme has recognised the
2000 file format it then works for all future files built in 2000.

The method we use for updating is standard and is usually achieved through
simply adding a percentage in the % complete field, or using the progress as
scheduled tool, or reschedule tool. My colleague has just come off a three
month overhaul project using Project 2003 without issues, and I simply resort
to using 2000 to avoid the issue. Also once we get over the problem by
opening and saving the original file in 2003, we have no further problems.
This seems to point less at user input issues and more toward some weird
interaction between 2000 and later versions.

Thanks though for your thouhjts any others would be most welcome.

Regards

DavidC

 

[John]

John,
Thanks for your reply.

Certainly is a head scratcher. we can open a Project 2000 file and save it
as a Project 2003 file. That is how we have got arround the problem. Having
made the save it allows us to make changes and update without any issues.

I recall last year having exactly the same problem with a Project 2000 file
that I opened on the clients machine using 2002 making changes and not being
able to save them, consequently loosing all the changes.

Another thought has crossed my mind that I will try. It seems that it
'fails' once and then doesn't happen again, ie it is non reproduceable. The
effect is almost like 'seeding'. Once the 2003 programme has recognised the
2000 file format it then works for all future files built in 2000.

The method we use for updating is standard and is usually achieved through
simply adding a percentage in the % complete field, or using the progress as
scheduled tool, or reschedule tool. My colleague has just come off a three
month overhaul project using Project 2003 without issues, and I simply resort
to using 2000 to avoid the issue. Also once we get over the problem by
opening and saving the original file in 2003, we have no further problems.
This seems to point less at user input issues and more toward some weird
interaction between 2000 and later versions.

Thanks though for your thouhjts any others would be most welcome.

Regards

DavidC

David,
Occasional type "failures" are perhaps the most aggravating and
difficult to deal with. It sounds like you have a workaround and that
may be the best you can hope for. I don't have any further suggestions -
maybe someone else has a bright idea.

John
Project MVP