Hi:

I need to turn off validation and I've seen some threads saying this
is not possible but my situation has a twist.

A customer needs the package to connect to different modem dialup
connections to connect to different servers (they use dialup for
security reasons). We have written two VB script tasks at the
beginning and end of a loop, with data flows in between. Before the
loop the dialup connection info is read into a recordset along with
Data Source connection information. The first script uses this
information to dialup and the last script hangs up the connection. The
problem is the package tries to validate the data connections and the
package has not dialed up yet, so it fails.

We managed to confirm it works in a test environment by putting a
break in the first script, manually VPNing into the test network (to
allow validation of the data flow to work), and then manually
disconnecting from VPN during the break. The script dials in and pumps
the data. But this won't be an option in production.

So if anyone has figured out a way to turn off validation, great.
Otherwise, any ideas to make this work? I was thinking about setting
up a dummy connection that would be connected outside the package
before running just for validation (and then the script would
disconnect to begin, but I would prefer to handle all of this within
SSIS.

Any help? While I see the point of validation it's a bummer that MSFT
didn't put this in the hands of the user.

Thanks, Kayda

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1212441&SiteID=1
Jamie answered you :D