That's the stuff -- thanks a million.
found out there. Kudos to you and your fellow authors.
"Allan Mitchell" wrote:
> Hello Mike,
>
> Ok So variables are different now. A child executable can see its parent's
> variables.
>
> Your child package can therefore see variables from the calling package (Scope
> allowing)
>
> If you want to set a child package property from a parent variable then have
> a look at "Parent Package Variables"
>
>
>
>
> Allan Mitchell
>
www.SQLDTS.com >
www.SQLIS.com >
www.Konesans.com >
> > I apologize if this question seems dumb, but I've looked at both the
> > group and the SSIS book and can't seem to find what I need.
> >
> > I have a package that takes input files from clients and loads the
> > data into staging SQL 2K5 tables. I've set up the connection manager
> > for each of the six source files to use variable values for the
> > connectionstring property, as the book suggested. The first step in
> > the package gets those values out of an SQL table, then the load steps
> > run. The key for that SQL table is a customer number.
> >
> > The parent package has a step that gets all the active customers, then
> > uses a ForEachLoop container to cycle through them and execute this
> > package.
> >
> > My two questions:
> >
> > 1) I cannot find anything in the Execute Package tasks that allows me
> > to specify the value for the customer number variable the child
> > package will use. How do I pass that value into the child?
> >
> > 2) How do I dynamically set the child package value so it executes the
> > development version when I'm testing new stuff and the production
> > version when it runs for the actual client stuff?
> >
>
>