• I finally was able to resolve this issue.

    Turns out that somehow 2 variables of the same name got created. When I looked at the variables though, it did not show that second variable until I clicked "Show all variables". One was created within the package scope and the other with the Execute SQL Statement scope.

    Once I deleted the variable inside the Execute SQL Statement scope, the package ran as it should.

    _______________________________
    [font="Tahoma"]Jody Claggett
    SQL Server Reporting Analyst
    [/font][/size]