Problem with opening older Project files in Project 2007

[Todd]

Hello,

I have a MS Project 2000 project plan that has 809 Actual Hours in
it. When I open the project in 2007 - just Open, not even Import -
the same exact project opens with 821.5 Actual Hours. We have
narrowed this down to certain individual tasks that have been changed
to Completed.

Each of the tasks that are affected have both actual work and
remaining work (as do others in the project plan). However, the
offending tasks have been changed to completed when opening them in
2007 and all of the remaining work was pushed to actual work.

In the time-phased views, these tasks have actual work against them
for every day leading up to the Finish date of the task - even if that
Finish date is in the future. So this is also a problem because a
user could create their timesheet in PWA and see weird values (like
4.394 hours per day) pre-populated for this task as actual work.

I've looked at these plans and am pulling my hair out because they
essentially look the same and I have no idea what setting in 2007
might be causing this. Does anyone have any idea what might be
happening here???

Thanks,

Todd

 

[Gary L. Chefetz [MVP]]

Todd:

Strange indeed. Do the talks in question have any data in the actual finish
date in the source plan? Are these summary tasks? Any commonality with task
type?

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Todd]

Hi Gary,

None of the tasks has a value in the Actual Finish column. None of
the tasks are Summary Tasks - they are all child tasks. I found that
there were actually 3 tasks in all that this occurred with.

All of the tasks are of Fixed Duration, non-Effort Driven. But every
task in the project plan is set up the same way.

The weird thing I just found was that the 3 tasks that this occurred
with were the only 3 tasks in the project plan that both % Complete
and % Work Complete were greater than 50% but were not 100%.

I don't know if that helps or just confuses things further.

Todd

 

[Gary L. Chefetz [MVP]]

Todd:

Without seeing the plan, it is difficult to diagnose. Could there be a
calendar difference? Fixed-duration tasks are particularly problematic by
nature and most often misapplied. If every task in the plan is fixed
duration, then you have a planning issue to deal with as life is not full of
fixed durations. Are these being tracked by percentage of completion or by
posting hours?

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Mike Mahoney]

Todd:

Without seeing the plan, it is difficult to diagnose. Could there be a
calendar difference? Fixed-duration tasks are particularly problematic by
nature and most often misapplied. If every task in the plan is fixed
duration, then you have a planning issue to deal with as life is not full of
fixed durations. Are these being tracked by percentage of completion or by
posting hours?

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:http://www.msprojectexperts.com
For Project Server FAQS:http://www.projectserverexperts.com











- Show quoted text -

Todd

Suggest you try exporting 2000 plan into different format say excel,
then open it in 2007.

regards

Mike