I haven't seen this problem since SQL Server 7.

Two ways of dealing with it

1. Drop a connection onto the Desiger | Choose "Existing Connection" | Choose from the dropdown the deleted connection | OK | Delete the connection
2. Save out to VB and then clean up and reimport.




--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

This is an issue in all versions, not just 7. Don't think it is a bug
exactly, just a feature of you changing the connection object used by an
icon. Happens to me when I'm not paying attention during a large package
development and a change my mind half way through about what each connection
is for etc.

Removing unwanted or orphan connections from a package
http://www.sqldts.com/default.aspx?6,222,253,0,1

Normally people notice it when the build a package from a saved VB file or
use the object model to load and save, forcing the layout information to
revert to the auto-layout default.

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

"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote