Jan said:
Hi,
Have you tried Task Information, advanced, check out "Mark task as
Milestone"?
I don't think Server will modify that setting.
HTH
--
Jan De Messemaeker
Microsoft Project MVP
+32 495 300 620
http://users.online.be/prom-ade
Think about it. If the task "was completed months ago", how could it
have zero duration? Did someone complete it instataneously? How did
they do that?
Remember that Project tries to follow some sort of "best practices"
with regard to scheduling. It's way more flexible that way than some of
us would like. It leaves it open for inexperienced users to cobble up
nearly meaningless schedules and then wonder why it's not working for
them. One of the "best practices" that MS sort of enforces is that a
milestone is a zero duration task, a marker in your schedule. In fact,
as Jan pointed out, Project will let you create a milestone with a
duration greater than zero. If I'd had any say in it's design, it
wouldn't do that! It's not good practice. Having the capability to have
non-milestones with zero duration is counter to scheduling practice.
Scheduling is actually a "discipline", meaning it has rules that apply
universally. If someone redefined the laws of physics and said
"F=1/2ma" instead of "F=ma", everyone would call them a nutcase. It's
not that way because Newton liked "F=ma" better, it's because he
observed it and measured it and that's why it's called a "Law". It's
what works in the real world. Physics is a discipline. So is
scheduling. And in that discipline called "scheduling", a zero duration
task is a milestone, by definition.
Hope this helps in your world.
