Scheduling Conflict in MSP 2007

[AMH]

I am new to project 2007 and am trying to help a project manager manage there
plan, the basic problem is that scheduling conflict does not appear to
operate the same way in project 2007 as it did in 2003, here an example that
is confusing me :

Task 1 duration 2 days
Task 2 duration 1 day must start 7th September, predecessor task 1 with a 2
day lag

Therefore if task 1 starts on 3rd September there is no conflict
However if task 1 starts 4th September or later then a conflict should be
highlighted by Microsoft project.

In Project 2003 the above happens as described and every time I make a
change to the start date of task 1 that would cause a conflict an error
message appears.

However in project 2007 the first time you make a change to the start of
task 1 then a conflict message appears, if you abide by the message, thus
pressing cancel and maintain the original date. The next time you make a
change to start date of task 1 that would cause a conflict no message
appears, thus my project manager who is limited in MSP experience can happily
make changes within her plan whilst ignoring any conflicts being introduced.

Is this a feature of 2007 or am I missing something in the way 2007 has been
configured/set up.?

Your thoughts would be appreciated.

 

[Jim Aksel]

I see the same behavior.
Set a deadline finish date on task b. You may do this instead of, or in
addition to, the constraint Start No Later Than.

Double click task b, pull the advanced tab and set a deadline for the task
finish.

If the deadline is violated, a red icon appears in the task information
column indicating a problem.
--
If this post was helpful, please consider rating it.

Jim
It''s software; it''s not allowed to win.

Visit http://project.mvps.org/ for FAQs and more information
about Microsoft Project

 

[AMH]

Thanks Jim, it gets round the problem, but basically means that duplicate
work will have to take place to add deadlines to all dates.

Does anyone know why this was changed in 2007 ?