October 28, 2021 at 6:33 pm
I am getting this for a simple SQL statement:
[Execute SQL Task] Error: Executing the query "" failed with the following error: "". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
update payments1
set [LineItem Amount] = replace([LineItem Amount],'$(','-')
It does not error for a similar statement.
Datatype is varchar.
Please help!
October 28, 2021 at 7:19 pm
For some reason it does not like the '$(' . I was trying to make the accounting () = -. I did it a different way and is fine now.
replace([LineItem Amount],'$(','-')
November 9, 2021 at 5:28 am
I am getting this for a simple SQL statement:
[Execute SQL Task] Error: Executing the query "" failed with the following error: "". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
update payments1 set [LineItem Amount] = replace([LineItem Amount],'$(','-')
It does not error for a similar statement.
Datatype is varchar.
Please help!
Within the Parameter Mapping window, the Parameter Name needs to contain an integer value, starting with zero, not the name of the parameter as defined in the stored procedure. This integer value maps to the question mark in the SqlStatement property.
You have one parameter to map, so you should use the value zero in the Parameter Name. The integer value used should map to the position that that parameter appears in the call to the stored procedure.
For example, if you add a second parameter to the stored procedure, you would first add another question mark to the SqlStatement property and then add a second parameter in the mapping screen with a value of 1 for the Parameter name.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply