Re: Changes not saved when altering dependency type

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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" <nobody@xxxxxxxxxxxxx> wrote in message
news:48f769d9$1@xxxxxxxxxxxxxxxxxxxx
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.

Gary Hollins wrote:
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" wrote:

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 wrote:
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" wrote:

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 wrote:
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.




.

Relevant Pages

  • Re: Changes not saved when altering dependency type
    ... It's serious if it occurs but as I pointed out the scenario being demonstrated is highly contrived. ... 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. ... From your post it isn't clear if you can repeat the problem in the server environment or if you create local files. ... 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 ...
    (microsoft.public.project)
  • Re: what health care reform would mean for the average worker.....
    ... course his taxes are higher because of the costs of the plan. ... and they had a really great relationship with the pediatrician ... When dave goes to his new pcp(his pcp also dropped him and also went ... happens today, with private insurance, pretty regularly ...
    (rec.sport.football.college)
  • Re: Changes not saved when altering dependency type
    ... It doesn't seem to be a problem really though because the scenario is ... From your post it isn't clear if you can repeat the problem in the ... You would be better placed to post this to the server newsgroup: ... Create a plan with a few tasks all linked together with finish-to-finish ...
    (microsoft.public.project)
  • Re: Changes not saved when altering dependency type
    ... I've stepped through your scenario and can reproduce what you report ... -Manually change link type through the Task Information dialog box. ... Save the plan ... Open the plan and the change to the dependency type has not ...
    (microsoft.public.project)
  • Re: Changes not saved when altering dependency type
    ... 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. ... In fact theonly people who weren't able to recreate the issue were those with MSP2007. ... Create a plan with a few tasks all linked together with finish-to-finish links ...
    (microsoft.public.project)