I have a stored procedure create for the sole purpose of launching a DTS
package. I can post the SQL later if necessary.

The problem is that I have multiple DTS packages that I would like to
execute in a SP. The sole purpose for this is that we have data stored and
being used in a foxpro database and I am writing Reports and would like to
have the data in SQL Server. So I created a SP that will accept a DTS
package name as a parameter, executes the package and continues on. Well...
my DTS package consists of a table drop, a table creation, a connection to
Foxpro, a query to retrieve the data and a connection to SQL Server.

If I run the DTS package directly from Enterprise manager, it executes
correctly. It drops the table (if it exists), creates it, queries the data
and drops it into the table. Pretty simple considering it was all done from
the "Import Wizard". The problem arises when I use my stored procedure to
execute the DTS package. It gets as far as dropping and recreating the
table, but never retrieves the data or populates the table. The stored
procedure does not error out or give me any signs of problems. In
actuality, it works perfectly fine for a VERY similiar DTS package for a
different table (which was also made from the "Import Wizard"). Both
packages do the same thing (drop, create, import) except they hit different
tables.

Does anyone know why this would happen? Any help would be GREATLY
appreciated.