I added two tasks (ActiveX and Dynamic Properties) for debugging purposes
which pop-up a few InputBoxes to enable me to test the rest of the DTS
package easily by manually providing values normally passed to the DTS
package by a VB application.

Once I've finished testing I'd like the simplest way to disable the two
tasks so execution begins at the first "real" (non-debug) package task. The
workflow looks like this:-

Task 1:ActiveX ----> On Completion ----> Task 2ynamic Properties ----> On
Completion ----> Task 3:Start Application Tasks

If I disable either Task 1 or Task 2 then Task 3 is never executed.

If I take out the workflow constraints, how can I guarantee that during
debugging they'll execute in the order Task1->Task2->Task3 and when "live"
the package will start at Task3?

At the moment I've got a Text Annotation that explains to the user to
disable Task 1 and Task 2 and then to delete the workflow constraints, but
this seems like a real pain. Surely there's a simpler way to include the two
debug tasks when debugging but which are easily disabled when the package
runs "live"?

You help is much appreciated.

Carl

Very quickly. I would do this a different way. I would have a controller
package that executed the Real package and passed any values to it that were
required. At release time I only need to suply the real package. Almost
like a test harness.

Allan

--

----------------------------
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



"Carl Revell" <carl.revell (AT) aylnews (DOT) no.spam.com> wrote

Allan,

Thanks. Your solution is simple and effective. I was so set on adding
debugging tasks to the beginning of the live package that I hadn't
considered simply creating a debug package that executed the live package -
duh!

Thanks again.

Carl


"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote