>Awhile back I asked the UT gang for some advice about running DTS packages from VB for a co-worker. The replies I got were correct and she was able to do this. However, she told me that what she ends up with is a gigantic code module that is essentially the SQL DTS package in VB form. All of the stored procedures she references in the DTS packages have been converted to full VB code. Does this not defeat the purpose of having stored procedures on the server to improve efficiency? Is there not a way to simply tell VB to execute the DTS package rather then issuing all the individual code? Of course, she might have done something wrong along the way; just wanted some input from others who may have already dealt with this. Thanks.

There is no need for that unless you want to go there. You can also create the package (with all steps in there) in the DTS designer, create a job that executes it (in SQL Server Enterprise Manager, right-click on the DTS package and select "Schedule") and then launch it with the sp_start_job stored procedure. That should be all that a client program would need to do in this scenario.

There are other ways to do this, but this one seems to be the simplest IMO. HTH