Opening Project 2000 file in 2003 gives different finish date

[getochkn]

I have a fairly large (2000 task) project done in project 2000. When it's opened in 2003, the finish date is off by two months. This has also happened on another machine (our printer's) and gave about the same result. Has anyone else experienced the same thing?

 

[PDQBach]

In some earlier releases there were some migration issues similar to what you experienced but I've never seen anything like that.

Same calendars? Same resource calendars? Same task calendars? Same default start time, end time, hours per day, hours per week, days per month? (Tools | Options | Calendar)

I'm grasping at straws here.

 

[PDQBach]

In some earlier releases there were some migration issues similar to what you experienced but I've never seen anything like that.

Same calendars? Same resource calendars? Same task calendars? Same default start time, end time, hours per day, hours per week, days per month? (Tools | Options | Calendar)

I'm grasping at straws here.

 

[getochkn]

I found out what the problem was I believe. All calendars, everything were set exact. My project calendar was a "Calendar days" with 7 days a week set. The problem was when project 2000 calculates the lag/lead time, it uses the project calendar, or in my case, the calendar days which means a 5 day lag was 5 calendar days. In project 2003, the lag/lead time will only use the project calendar unless the successor has it's own calendar (which it does-5 day a week calendar with holidays added) so it uses that calendar to calculate lead/lag duration, so a 5 "calendar day" lag in project 2000 becomes a 5 "working day with holidays" lag in project 2003.