I am writing a tool to convert DTS packages by using the scripting model. I
have to change the connections in multiple ways. Some packages are behaving
weirdly with their connections: in de original package there are only the
connections visible that are used in that packages, but in my converted
packages also a lot of removed connections are visible.
Some observations:
1. This is for every type of connection, mainly SQL Server, Oracle and text
files.
2. When I iterate over the connections (package.Connections) in the
original packages these connections are there already, although they're not
shown in the designer.
3. Even when I remove the previous versions of these packages the
superfluous connections remain. Also I'm only getting the latest versions of
the packages (PkgSQLServer.EnumPackageInfos("", true, "") ).

Now I'm modifying my tool to see which connections are not being used and
then remove them. But any other solution - or just an explanation ) would be
appreciated!

Thanks in advance,
Gaston Verelst

Gaston Verelst wrote:
They are fairly easy to create.

Removing unwanted or orphan connections from a package
(http://www.sqldts.com/default.aspx?253)


--
Darren
http://www.sqldts.com
http://www.sqlis.com