I have this block of code that is in a child package (see below).

The idea is, I want to be able to run the child package by calling it from the parent packageAND sometimes I want to be able to run the child package on its own, in which case it will not have access to the variables in the parent package, i.e. "TEST". That is, the"TEST" variable will not be "seen" by the child package because the TEST variable lives at the parent level, not the child level.

In the case of running the child package on its own, it won't find the TEST variable, and it should fail.

However, I do not want the script task to fail as I have a try catch block but it fails anyway even with the exit try. What am I missing please?

Thank you.

Try
Dim vars As Variables
Dts.VariableDispenser.LockForWrite(“TEST� 'this is a variablein the parent package
Dts.VariableDispenser.GetVariables(vars)
Try
vars(“TEST�.Value = “I’m Done�br>
Catch ex As Exception
Throw ex
Finally
vars.Unlock()
End Try
Catch ex As Exception

�what can I put here so that the script task does not fail?

Exit try
‘Throw ex - do not want this
End Try

In my testing, it didn't seem to matter how the error was handled in the script- it still propagated the error to the package.

Another, even easier approach to resolving this - check for existence of the variable before trying to lock it. You can use the VariableDispenser.Contains method for this:

Why not go ahead and create the variable in the child package as well? You can set it to a default value in the package. Then use a parent package variable configuration to set it when it is called from a parent. That way the variable always exists, and if it has the default value, you know it wasn't set from the parent.

Thanks that helps, do you have a link that explains how to set up a "parent package variable configuration" ?

p.s. Do you know why the Try-Catch returns an error in the above example?

Parent Package Variables: http://technet.microsoft.com/en-us/library/ms345179.aspx

No, I'm not sure. I tried a quick test and got the same results as you - I'll play with it a bit more this weekend.

From the CATCH block, try doing the following.

Code Block

Dts.TaskResult = Dts.Results.Success

In my testing, it didn't seem to matter how the error was handled in the script- it still propagated the error to the package.

Another, even easier approach to resolving this - check for existence of the variable before trying to lock it. You can use the VariableDispenser.Contains method for this:

Thanks!