Hi

I am trying to re-write and old SQL 2000 DTS package for SSIS using VS
2005, but so far I have not been able to complete the task as each time
my package gets completely corrupted by VS.

Here is what usually happens:

1. I add a Data Flow Task to the Data Flow tab
2. Then I double-click it to edit it
3. I add a Data Flow Source (usually a Flat File Source) and set up a
Connection Manager for it
4. Then I add a SQL Server destination and map columns (occasionally I
have to also add a Data Conversion or Script transformation

5. I save the package
6. Then I right click on the designer surface and select Execute Task

I can usually repeat these steps several times to add one or two Data
Flow Tasks, but invariably eventually when I get to step 6 and try to
execute the task nothing happens (i.e. the environment enters into the
Debug mode but the data flow steps are not being highlighted from
yellow to green or red, but the status bar says that the task has
completed). No data is copied to the database, and no matter what I try
I cannot get it to run. So, then I close the package editor.

However, when I open the package all the transformation tasks that I
created for the most recent Data Flow Task have disappeared.
Surprisingly the Connection Manager is still there, but if I try to
edit it, I get: "Flat File connection manager could not be edited".
Source, but when I click on the Flat File Connection Manager I get a
list of GUIDs instead of manager names.

This has now happened to me several times. I hope there is a fix or a
workaround for it, as without being able to migrate my DTS packages, I
will not be able to migrate my database to SQL 2005.

So far, I have not come across anyone who has come across this problem
and I would be VERY grateful if someone came up with a suggestion.

Thanks for your help.

mike