AHA!
I've found that if I attempt to execute an execute dts package task
from within an open dts package (inside the mmc editor for dts), most
all transform data and data drive query tasks will signal an error if
follwed by an execute sql tasks. If I run the parent packaage by
executing it from the dts local packages explorer, the parent and
child packages will all run with no errors.
So there's a problem in trying to run nested dts packages from the
editiable window.
I hope our friends at The Borg will attend to this issue. In the
meantime, execute your parents when you aren't editing them.
later,
dirk
[quoted text, click to view] dirkStone@excite.com (Dirk Aubrey) wrote in message news:<28a9b676.0404061037.1417255d@posting.google.com>...
> This is a non-VBscript issue.
>
> I have a package (PACK1) which has two tasks.
>
> The first is a single transform data task that copies rows between two
> identical tables. The transformations are 3 copy column type.
>
> The second task is an execute sql task that truncates the 2nd table.
>
> The workflow from 1st to the 2nd is on completion only.
>
> Both tasks/steps are set to execute on main thread (value = -1 in the
> disconnected edit window).
>
>
> This runs fine.
>
>
> If I create another package (PACK2), and within it create a single
> execute package task which calls PACK1, that's when I see the error.
>
> I've tried this on two separate servers, with the same result. As far
> as I know, there is no VBSCRIPT involved in anything here.
>
>
> These are both SQL2000 running on WindowsXP.
>
> Any ideas appreciated. Thanks in advance.
>
> thanks