Check to see that all your subtasks have a minus (are visible). Change the dates accordingly and this will change the milestone dates to reflect.
NoWhereMa wrote:
Unalbe to Change Milestone Dates
02-May-07
I am updating a Project Plan in Project 2003 and the dates for the
milestones seems to be locked. I can change the overall project date and
even the individual tasks but not the milesones.
I attempted to manually change the milestone dates but the fields are
locked. I next tried selecting the 'task information' option and then
advanced, then modify the deadline. The deadline modfied/changed but again
the fields are locked and dates remained the same.
When I do change a task date I get the error message 'Entering a start date
is not the best way to schedule this task:' and it give me a few options.
Can anyone assist on how to change the milestone date, I must be missing
something obvious. Thank you in advance
Previous Posts In This Thread:
Unalbe to Change Milestone Dates
I am updating a Project Plan in Project 2003 and the dates for the
milestones seems to be locked. I can change the overall project date and
even the individual tasks but not the milesones.
I attempted to manually change the milestone dates but the fields are
locked. I next tried selecting the 'task information' option and then
advanced, then modify the deadline. The deadline modfied/changed but again
the fields are locked and dates remained the same.
When I do change a task date I get the error message 'Entering a start date
is not the best way to schedule this task:' and it give me a few options.
Can anyone assist on how to change the milestone date, I must be missing
something obvious. Thank you in advance
Re: Unalbe to Change Milestone Dates
Hi NoWhereMan,
Welcome to this Microsoft Project newsgroup
Your milestone should be logic linked to a predecessor task that drives the
milestone. If you typed in any Start Dates for the tasks and/or Milestones,
Project will have set up a constraint. Add a predecessor link and in
Project/Task Information/Advanced tab, ensure that the Constraint Type is As
Soon As Possible (ie no constraint).
FAQs, companion products and other useful Project information can be seen at
this web address:
http://project.mvps.org/faqs.htm
Hope this helps - please let us know how you get on
Mike Glen
MS Project MVP
See
http://tinyurl.com/2xbhc for Project Tutorials
Re: Unalbe to Change Milestone Dates
NoWhereMan wrote:
What do you mean by the term 'milestone'. In Project terms, a milestone
is an event that means that the Project has reached a certain state.
Therefore, milestone dates (using that definition) are determined by the
elements of work that have been completed and the underlying linking logic.
It sounds as though you might mean deadline. If that is the case, you
enter this in the deadline field from the advanced tab of the task
information dialogue. Deadline in this context means an externally
imposed date when it is required that something be completed.
If you really do want to move milestones, then you can do so by setting
must start/must finish etc constraints on them. You will get the
warnings you have already encountered but it does work. For what it's
worth, you can also enter lag times on the linking logic. Normally this
approach would be bad practice however.
Not sure why you say adding a lag on a link to a milestone is bad practice?
Not sure why you say adding a lag on a link to a milestone is bad practice?
For example after a task "order equipment" I would add a milestone
"Equipment received" with a lag equal to the delivery period. Most events do
of course happen immediately after a task has finished.
--
Rod Gill
Project MVP
Project VBA Book, for details visit:
http://www.projectvbabook.com
NEW!! Web based VBA training course delivered by me. For details visit:
http://projectservertraining.com/learning/index.aspx
----------------------------------------------------------------------------------------------------
Re: Unalbe to Change Milestone Dates
Rod Gill wrote:
If I said normal practice would you be happier? The example you give is
one of the few standard instances in which you would adopt this
approach. It would be bad practice if used as a device to indicate
deadlines.
Another situation in which I use it is to allow for a period of running
for a new system before it is deemed to be stable.
The point is that it measures a state change and that can be physical or
conceptual.
Dave
No probs, certainly deadlines are best for communicating a date that has to be
No probs, certainly deadlines are best for communicating a date that has to
be met.
Happy scheudling!
--
Rod Gill
Project MVP
Project VBA Book, for details visit:
http://www.projectvbabook.com
NEW!! Web based VBA training course delivered by me. For details visit:
http://projectservertraining.com/learning/index.aspx
----------------------------------------------------------------------------------------------------
Submitted via EggHeadCafe - Software Developer Portal of Choice
ASP.NET DATASET Vs ASP RECORDSET SPEED TRIALS
http://www.eggheadcafe.com/tutorial...fd-0a854d469ee7/aspnet-dataset-vs-asp-re.aspx