Fixing a date on a milestone w/external dependencies

[Mike]

Does anyone know of a way to "Fix" the date on a milestone
with external dependencies? For example, I have a date of
01/30/04 on my predecessor milestone but the date for my
cross-project successor milestone changed to 01/15/04.
The tool seems to be accepting this change to the
successor and pulling my predecessor date back to 01/15/04
to alleviate the dependency violation. Is there any way
to have the ability to allow the successor to change
without affecting the date on the predecessor? Basically,
I'd like to see the violation in a view/report of some
sort before allowing the predecessor milestone to move
in/out. If anyone out there can help me figure out how to
make a date "stick" no matter what the tool thinks should
happen, please let me know. Thanks

Mike

 

[Gérard Ducouret]

Hello Mike,
You have to use a "hard" constraint such as "Must Start On" or "Must Finish
On" on this milestone.
Double Click on th task name, then in the Takinformation dialog, got o the
Advanced tab : select a Constraint Type.
If a dependency violation happens, you can set an alert : display the Total
Slack field (which will appear with negative value) or display the negative
slack graphically in the Gantt Chart.

Hope this halps,

Gérard Ducouret