Changes not saved when altering dependency type

[Gary Hollins]

msp pro 2003 (sp3)

Scenario

Create a plan with a few tasks all linked together with finish-to-finish
links
Save the plan
Optionally closed and reopen the plan at this point for completeness
Clear the current links and re-link as finish to start links
Save the plan
Close the plan
Open the plan and the change to the dependency type has not been saved


One of our programme’s planners found this problem with one of our program
plans and original thought it was something wrong with the project not saving
to the server. However as described above the problem is entirely repeatable
and apparently happens to every project file.

Has anyone come across this or have any recommendation on how to discover
which changes have not been saved.

 

[Dave]

This is not a generic problem with Project 2003.

From your post it isn't clear if you can repeat the problem in the
server environment or if you create local files.

You would be better placed to post this to the server newsgroup:

microsoft.public.project.server

 

[Gary Hollins]

Apology for the lack of clarity.

This problem occurs in local files. I mentioned perhaps a bit too much
background which may have been misleading.

Follow the scenario in my original thread.

Since my original posting a few consultants within my company and one of my
clients were also able to repeat the problem.

 

[Dave]

How are they able to recreate it? I have never seen it and can't create it.

Is it a 'state' that the file gets into and once this errant behaviour
starts to manifest itself is it the case that all tasks exhibit this
behaviour?

Is it a file corruption thing - have you tried the recommendations for
resolving that?

 

[Gary Hollins]

My collegues and clients are all able to recreate the problem by following
the scenario I detailed above. They started with a new blank project file so
it not a corruption issue.

So far about 10 people from different companies with different computers on
different networks even in different countries have all seen this problem
when following the scenario I explained. In fact theonly people who weren't
able to recreate the issue were those with MSP2007. I can't help but feel
this is a generic problem with msp pro 2003.

Note when following the scenario if you have auto calculate switched off it
appears (when looking at the gantt) that there is no problem. But if you look
at the predecessor column you can see the dependencies are still "FF"
dependencies and the if you hit refresh the gantt will be updated.

 

[Dave]

OK, the crucial bit of information that was missing was that I had to
look in the predecessor column. I can now recreate it. It seems that
the link type is actually saved correctly, but that the labels
associated with it are incorrect both in the predecessor column or in
the dialog box obtained by double clicking the link.

It doesn't seem to be a problem really though because the scenario is
fairly contrived.

There is no chance of getting this 'feature' fixed in any case.

 

[JulieS]

Hi Gary,

I've stepped through your scenario and can reproduce what you report
using Project 2003 (SP3). The only way I seem to be able to get the
FS changes to "stick" is to:

- Manually re-enter the predecessor IDs
or
-Manually change link type by double-clicking on the link line and
changing through the Task Dependency dialog
or
-Manually change link type through the Task Information dialog box.

Using the unlink and link tasks button does not appear to work
correctly.

I hope this helps. Let us know how you get along.

Julie
Project MVP

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

 

[JulieS]

Dave. It's a bit more serious than you seem to note. Press F9 to
recalculate and watch the schedule change to reflect FF links. The
link type is *not* saved correctly in my testing.

To your comment about "There is no chance of getting this 'feature'
fixed in any case" -- I didn't realize you worked for Microsoft and
could control what fixes were implemented.

Julie

 

[Dave]

Dave. It's a bit more serious than you seem to note. Press F9 to
recalculate and watch the schedule change to reflect FF links. The
link type is *not* saved correctly in my testing.

It's serious if it occurs but as I pointed out the scenario being
demonstrated is highly contrived. Hence it is unlikely to be a
significant issue unless it can occur in more routine usage.

To your comment about "There is no chance of getting this 'feature'
fixed in any case" -- I didn't realize you worked for Microsoft and
could control what fixes were implemented.

Julie

What do they say about sarcasm being the lowest form of wit?

I may or may not work for Microsoft - you've got no way of knowing.
Nevertheless, you'll just have to wait and see if I am right or not. If
you think you know better perhaps you could express that without the
smart-alac comments.

 

[JulieS]

It's serious if it occurs but as I pointed out the scenario being
demonstrated is highly contrived. Hence it is unlikely to be a
significant issue unless it can occur in more routine usage.

Dave, it appears anytime a user attempts to change a link type from
FF to FS in any project file. I don't feel that the desire to
change link types in "highly contrived" nor would I expect a change
in link type not be retained when a file is saved and closed. The
file doesn't need to be all FF links, it occurs in a file with mixed
link types.

What do they say about sarcasm being the lowest form of wit?

I may or may not work for Microsoft - you've got no way of
knowing. Nevertheless, you'll just have to wait and see if I am
right or not. If you think you know better perhaps you could
express that without the smart-alac comments.

Sorry, I forgot the I hope this helps.

<snip>

 

[Gary Hollins]

Hi Dave

I am glad you are now able to understand the problem

I appreciate that you might feel the situation was contrived but it was
uncovered in a very real situation. I'll bet it has happened to other people
as well but they either missed the dodgy planning feature or they just put it
down to a msp quirk and wholesale replaced the tasks with new ones.

 

[Gary Hollins]

Thanks Julie,

To be honest all is well now that we understand to be wary when changing
dependencies.

PS - I wonder what Dave meant by a 'smart alac'? Perhaps a smart version of
one of these?

ALAC may refer to:
Apple Lossless, a digital audio format
The At-Large Advisory Committee, a committee of ICANN
Artificial Limb & Appliance Centre - Centre hosting the Artificial Limb &
Appliance Service of Wales

 

[JulieS]

You're welcome Gary. I'm glad you pointed the issue out. Just so
you know, in further testing the problem doesn't appear to be
restricted to FF links. The problem occurs when changing any type
of link other than FS.

PS - I'm going for the At-large Advisory committee

Julie