I've got a DTS package that populates several tables in an
Access database from SQL 2000 tables (all in the same
database). The destination Access database is supplied as
a skeleton that is copied into place in an earlier
package. The data transform occurs in multiple steps, one
for each table (about 10 in all).

When I run this package manually, either remote or logged
in to the server, everything works perfectly. When I
schedule this package by itself, everything works
perfectly. But when this package is called from a larger
package strange things happen. The first table is copied,
but none of the others do, and the package returns
successful.

Why would a DTS package stop midstream, and without
failing? It can't be a permissions issue because of the
partial successful write to the Access database.

Please help!!

Richard

I had a similar problem once - I discovered I was calling the right package, but on the wrong server! Make sure your package task is calling what you want it to.

Thanks for the input, but everything here is running on
the local server. I've had that problem in the past where
packages on our test server executed packages on our
production server, but that's not the case here.

Any other thoughts, folks?

RichW

your package task is calling what you want it to.