Feedback
Did this article resolve your question/issue?

   

Article

Error occurs when running a SQL task with SSIS using the ADO.NET provider.

Information

 
TitleError occurs when running a SQL task with SSIS using the ADO.NET provider.
URL NameResult-binding-by-name-Max-UPD-DATE-is-not-supported-for-this-connection-type
Article Number000177045
EnvironmentProduct: Connect for ADO.NET DB2 provider
Version: 4.2
OS: Windows
Database: DB2
Application: SSIS 2008
Question/Problem Description
Below error occurs when running a SQL task with SSIS using the ADO.NET provider and the ResultSet option is set to Single row.
Steps to Reproduce
Clarifying Information
Error MessageError: An error occurred while assigning a value to variable "Last_UDTDATE": "Result binding by name "Max_UPD_DATE" is not supported for this connection type. "
Defect Number
Enhancement Number
Cause
Resolution
In the SSIS SQL Task Editor, change the 'Result Name' field in the 'Result Set' tab to the index of the column in the result set like 0 or 1 instead of the column name.
Workaround
Notes
Last Modified Date8/17/2016 2:25 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.