While reviewing the white paper that describes the recent Project 2007 Infrastructure Update in detail, I came upon some interesting information at the end of the document.

Before I start, I first want to thank and congratulate Microsoft on a job well done with the quality and quantity of documentation they’ve provided for this update. Compared to the sometimes-cryptic KB Articles that typically accompany hotfixes and updates, the Infrastructure Update’s documentation is outstanding.

That being said, I do have some concerns relating to the changes in Cost Resources, which are a new way in Project 2007 of accounting for costs associated with a project. Cost Resources are typically used to account for non-work costs such as travel expenses. The Infrastructure Update makes some significant changes to the way that Cost Resources function, and while I am a big fan of the idea of Cost Resources, I cannot help but be concerned by some of the caveats I’ve quoted below:

For those of you that haven’t heard yet, yesterday morning Microsoft released the long-awaited Infrastructure Update for WSS, the Office Servers (including Project Server), and Project 2007.

You can read an overview of updates here, and read detailed information in this white paper.

This update promises significant performance and stability improvements to the entire line of Office Servers, WSS, and the Project Client. If you haven’t already (or have only read the overview), I strongly recommend you read the white paper. It contains 30 pages of information about the update, and contains a lot of important information (including user scenarios to avoid).

From the overview:

Project Server

• Timesheets and My Tasks stability and usability improvements
• Queue Management user interface improvements
• Logging Tracing improvements
• Project Server performance improvements
• Project Server 2003 to Project Server 2007 migration fixes

Earlier today in the EPMFAQ Forums, there was a discussion concerning an issue in Project 2007 whereby the Duration on a Fixed Duration task is set to 0d if the Work on that task either rolled up or was set to 0h.

This is divergent behavior from Project 2003, and one that appears to be causing issues for a rapidly increasing number of users. Many of us within the community have been aware of this issue for quite some time, but there appear to be many people that are unfamiliar with this little conundrum, be they users, administrators, or consultants.

Here’s my response to the question:

The issue you are referring to manifests when the Work for the task is set to 0h, whether by rollup or entry. This results in the task’s Duration being set to 0d. This is true for all Task Types, including Fixed Duration.