I can not get my global variables to update.

For a simple Execute SQL Task, I mapped the variable to the global variable
in the Result Set page. Name = 0 Variable = User::SQL_RecCount. When i look
at the variables tab, the value has not changed

The value displayed in the Variables tab will ALWAYS show the Design Time
value of the variable, even though the package may have run and assigned it
something different. After execution, the value reverts back to that assigned
initially.

Try this: Set a BreakPoint on the PostExecute event of the Execute SQL Task.
When the package hits the break, examine the contents of the variable using
the Locals window.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Marty" wrote:

The value displayed in the Variables tab will ALWAYS show the Design Time
value of the variable, even though the package may have run and assigned it
something different. After execution, the value reverts back to that assigned
initially.

Try this: Set a BreakPoint on the PostExecute event of the Execute SQL Task.
When the package hits the break, examine the contents of the variable using
the Locals window.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Marty" wrote:

The value displayed in the Variables tab will ALWAYS show the Design Time
value of the variable, even though the package may have run and assigned it
something different. After execution, the value reverts back to that assigned
initially.

Try this: Set a BreakPoint on the PostExecute event of the Execute SQL Task.
When the package hits the break, examine the contents of the variable using
the Locals window.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Marty" wrote:

The value displayed in the Variables tab will ALWAYS show the Design Time
value of the variable, even though the package may have run and assigned it
something different. After execution, the value reverts back to that assigned
initially.

Try this: Set a BreakPoint on the PostExecute event of the Execute SQL Task.
When the package hits the break, examine the contents of the variable using
the Locals window.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Marty" wrote:

The value displayed in the Variables tab will ALWAYS show the Design Time
value of the variable, even though the package may have run and assigned it
something different. After execution, the value reverts back to that assigned
initially.

Try this: Set a BreakPoint on the PostExecute event of the Execute SQL Task.
When the package hits the break, examine the contents of the variable using
the Locals window.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Marty" wrote:

The value displayed in the Variables tab will ALWAYS show the Design Time
value of the variable, even though the package may have run and assigned it
something different. After execution, the value reverts back to that assigned
initially.

Try this: Set a BreakPoint on the PostExecute event of the Execute SQL Task.
When the package hits the break, examine the contents of the variable using
the Locals window.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Marty" wrote:

The value displayed in the Variables tab will ALWAYS show the Design Time
value of the variable, even though the package may have run and assigned it
something different. After execution, the value reverts back to that assigned
initially.

Try this: Set a BreakPoint on the PostExecute event of the Execute SQL Task.
When the package hits the break, examine the contents of the variable using
the Locals window.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Marty" wrote:

The value displayed in the Variables tab will ALWAYS show the Design Time
value of the variable, even though the package may have run and assigned it
something different. After execution, the value reverts back to that assigned
initially.

Try this: Set a BreakPoint on the PostExecute event of the Execute SQL Task.
When the package hits the break, examine the contents of the variable using
the Locals window.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Marty" wrote: