But changing the default start time does NOT cause new tasks to start at
5am - that's my point. The Default Start field only applies to designate
the assumed time when a date is manually typed into a start field without
typing the time and does not otherwise affect the times tasks will be
scheduled to start. The only time it will appear to set a start is if a
date is typed into the Start field thereby setting a SNET constraint. When
you examine the constraint it will in fact show the typed date plus the
default field time as the constraint date.
I'm betting that something like this has happened ... the reason the
existing tasks start at 8am is probably because when he set the project
start date the working time calendar said hours were 8 to 5. So this was
carried over into project start field and it probably says the project
starts on "mm/dd/yy 08:00am." Now sometime later he's changed the working
time calendar to the 24 hour calendar but has neglected to change the
project start date TIME component to reflect an earlier hour. So now
although according to the calendar tasks could start as early as 12:01am
they don't because the project kickoff, the time the first task should
begin, is still defined as 8am, 8 hours later. Because the project doesn't
offically start until 8am, the first tasks don't begin until 8am, and all
subsequent tasks key off of them.
The only way to get it to work as you suggest is to set the default start
to, say 5am, and click "set as default" as you suggested BUT that will not
set back the project start to 5am. After making the default start time 5am
he has to start a brand new project file for it to be picked up as the
project start time. It's simpler simply to go in and edit the project start
to show the kickoff time to be the time he wishes the first tasks to begin.