There is a sql task in a dts package that runs a stored procedure which fails
on a primary key constraint while inserting a duplicate row.

If the package is run from the dts designer, it reports an error and follows
the 'on failure' path.

If the package is run with the dtsrun command from a job. the package
reports success and follows the 'on success path'.

I can not find a reference to this in the kb articles. I've also noticed
that this behavior works correctly in sql 2000. I just need a work around for
existing sql 7.0 jobs.

I've been waiting sind 12/21 for an answer to this question. Can someone
please reply.


"Jo" wrote: