Hi,

I've just built a few packages and then found out that I needed to fo
through and change all of the task and step names which I have done
through using disconnected edit. However this deleted all my
precedents which I have re-created but now when I run the package only
the first step runs and then it says the package has been successful
but none of the other steps have been run.

If I copy some of the steps into a new package, re-name then and then
set the precedents it all runs ok. Is there a way that I can get the
package to "refresh" itself as it seems to have also held any previous
precedent constraints and hence got confused about what it is supposed
to execute next. I don't really fancy having to re-write these
packages if possible.

TIA

Leyton

Have you remembered to rename the TaskName property of the steps to the
relevant one ?

--
--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"NoName" <menb31 (AT) dsl (DOT) pipex.nospam.com> wrote

In article <e3c1mvoqn0qhbhrntkfam4pk8fua1fvtgb (AT) 4ax (DOT) com>, NoName
<menb31 (AT) dsl (DOT) pipex.nospam.com> writes
The action of renaming your tasks and steps (you did do both) will not
have deleted anything but you have broken it.

Personally I always rename tasks as soon as I add them. If I do it
afterwards I delete any precedence constraints leading from the task.

There are four places to rename, but remove the constrains leaves only
three.

Task Object
- Task Name property

Step Object
- Step Name property
- TaskName property (Relates step to task)


Each step has a Precedence Constraints collection, within which can be
zero or more precedence constraint objects. The precedence constraint is
held by the destination step, and there is a StepName property that
tells the constraint the source step. I delete constraints because you
rename step a, but you must then change the constraint held by step b,
and it is just to much of a pain to find it.

Deleting a constraint does not delete any Workflow ActiveX Script you
may have added, since this is held on the destination step, not the
precedence constraint object itself.



--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org