Hi, I tried yesterday similar approach by dropping on the DTS design surface

a. SQL Server connection

b. Two Execute SQL tasks

c. ActiveX script task with

I. on completion workflow constraints pointing from both Execute SQL tasks

II. script that would try to determine the timing when the execution context was passed to ActiveX script

Here is assumption tested:

* DTS constraints connected by logical AND operator ( or so I believe )

* Such a data construct reaches its decision to proceed to next step after all constraints pointing to the same component executed and match constraint declared condition

I ended up turning on profiler and the trace indicated that both ExecuteSQL components were running on the same SPID ( this was happening under the hood, the two queries ran sequentially )

I added the second SQL Connection component on the designer surface, set ExecuteSQL task to point to distinct connection and the issue went away. On with test for OnCompletion constraint timing.