"David Norman" wrote:

> I have created a package that contains a script task that uses a connection
> manager. The name of the connection manager was specific to the data source
> and I want to make my package deployable, so I rightclick-renamed the
> connection manager to something more generic and stored the details in a
> config file.
>
> However the script task failed to connect using
>
> Dts.Connections("Generically Named Connection
> Manager").AcquireConnection(Nothing)
>
> While attempting to debug I tried creating a new connection manager - and lo
> and behold, the old connection manager name is listed as "previous connection
> information". I selected it and changed the script task to use the old name,
> and everything works as before.
>
> However I don't really want to use the old connection manager name as it
> would be very confusing in a test/prod environment. What's my workaround for
> this? Is there somewhere I can dive in and force the name change?
>
> Thanks in advance,