What tasks do you have listed in your package?  Do you have multiple versions of the package created (i.e., have you changed/saved it multiple times)?  If you have multiple versions...

If you are using VB6, I recommend you just use the following syntax:

Set DTSObj = Nothing

Have you tried this option?

What version of SQL Sever are you running?  SQL Server 2000 error logging is very intuitive and will provide src/dest error rows in separate text files if possible.  If you...

I second that.  Create a table that stores all of your path/file information and use that in conjunction with the Dynamic Properties task.

Which version of SQL Server are you using?  If you are using SQL2000 have you looked at the Copy SQL Server Objects task?  Does your office use a WAN?

Is the package going from SQL7 to SQL2000?  I've had conversion issues before when trying to design a package on SQL7 and moving to SQL2000 and vice versa.

Try putting some of this code together to make it work for you...these are some snippets of stuff I have previously worked on / played with:

Dim adoConn, adoCmd, adoRst

I don't understand your question...you can have 2 connections to 1 file...both connections are setup referencing the same file, but they are broken out as 2 connection objects in DTS. ...

It is not possible, to my knowledge, to place a specific piece of data into a specific cell in Excel via Transformation Task.

However, you can accomplish this task using an ActiveX...

1.  If you create a separate "Text File Source" connection for each transformation, it will work properly.

2.  Same answer as above...keep both transformations in the same package.

3.  You can achieve this...

If both servers are SQL2000 servers, just use the native SQL Server connections within DTS.  I feel that will be your fastest option.  You can then also create a job...

Are both the DB's on SQL Server platform's?  If so, there is native connectivity associated between linked servers and DTS packages if configured correctly.  Personally, I'd use a DTS...