I have a DTS where an Execute SQL task precedes an ActiveX Script task. The
workflow between them indicates that the Execute SQL Task must complete
successfully before proceeding to the ActiveX Script task. However, the
Execute SQL task is not completing before the ActiveX Script task begins,
which is leading to DTS failure. I have indicated in the workflow
properties for the Execute SQL task that the results for it should be
committed upon completion. Any advice? Thanks in advance.

So you have it looking like example 1 here

Introduction to Workflow
(http://www.sqldts.com/default.aspx?287)

What is in the ExecuteSQL task?


--

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



"Serena" <sh (AT) syr (DOT) edu> wrote

Yes, it's like example 1 in that link. The Execute SQL task is a series of
update/delete statements that clean the data in a single table -- e.g.,
removing certain characters, deleting a header row (if there is one), etc.
The data needs to be cleansed before it moves on to the next step.

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

What happens if you break up the n statements in the single ExecuteSQL task
into multiple tasks connected by workflow ?

--

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



"Serena" <sh (AT) syr (DOT) edu> wrote

Just tried that, and it didn't work.

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