Hi,
I'd like to rename all the objects in my packages in order to make the
DTS-produced logs more @readable@ before I produciton-ise my system.

I tried doing this using Disconnected Edit which seemed to work fine
until I then double clicked on one of my tasks (as normal) and got the
following:

"Task 'DTSTask_DTSExecutePackageTask_1' was not found"

Anyone any ideas how I can change the names of the objects in my
packages and still be able to edit them all.

TIA

Regards
Jamie



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

In article <u1sEr6ffDHA.2332 (AT) TK2MSFTNGP12 (DOT) phx.gbl>, Jamie T
<Jamie.Thomson (AT) int21 (DOT) com> writes
Jamie,

There are four places to rename, but if you remove constrains it leaves
only
three.

-Task Object
#1Task Name property

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


#4
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.



For a large package it can be quicker to save it to a VB file (Save VB
from package menu), and use find and replace. You then compile the VB to
save it back to a DTS package.

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

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

Thanks Darren,
I had a bit of trouble with the constraints. After I'd changed the other
3 values my precedence collections contained 2 items, the first of which
had StepName equal to the previous name of the preceding step.
It was easy to change it to what it should be but then I was left with
the precedence constraints in my precedence collection which were
exactly the same. This worked fine but it was a little "dirty". Getting
rid og them was easy though. I just double-clicked on a precedence
contraint in the GUI and then immediately clicked [OK] without making
any changes. The upshot of this was that my precedence collection(s)
only contained 1 item whereas before they contained 2.

All working fine now. Thank you very much for the advice.

Jamie Thomson



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!