Errata

Microsoft Project 2013 Step by Step

Errata for Microsoft Project 2013 Step by Step

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
PDF Page 74
end of the 1st paragraph

Text says: As soon as you set task 6 to automatic scheduling, however, Project did just that and adjusted the start date of its summary task as well .
Actually Project doesn't adjust the start date of the summary task, as far as task 7 still manually scheduled.

Boris Malyov  Feb 22, 2014 
Printed Page 398
Step 11

The shading described in step 11 will not work unless the cells in the table are selected first. The new cells are not automatically selected when they are added to the table.

 Brian Huffman  Nov 12, 2013 
Printed Page 408
Screen shot at the top of the page

The screen shot shows a title for the report on the left edge and in a text box. The text box may appear automatically in Project Professional (I don't know about that), but it does not appear in Project Standard.

 Brian Huffman  Nov 13, 2013 
ePub Page 2884 of 9539 (ebook)
The Exercise in Adjusting Working Time for Individual Tasks (Chapter 9)

Chapter 9: "Adjusting Working Time for Individual Tasks"

In the "scenario" setting up the exercise for this section, it states that the color-setting services firm "starts new jobs only on Mondays through Wednesdays". That implies that they still work on Thursdays and Fridays, but only work on existing jobs at the end of the week. However, the exercise's solution is to adopt a calendar that bars *any* work for this task on Thursdays and Fridays. From the scenario that's described, that's the wrong solution.

Notwithstanding whether the scenario description needs to be changed, it raises an interesting larger question, how could you create a situation which forces a task or even a resource to avoid starting on certain days, but still allows it to continue a task's work on those same days?

I'd appreciate a direct email reply, even if you don't publish this as an errata.

 Scott Reed  Apr 12, 2013