Feedback
Did this article resolve your question/issue?

   

Article

Subsequent executions of a stored procedure fail with no error message with Connect for ODBC SQL Server driver

Information

 
TitleSubsequent executions of a stored procedure fail with no error message with Connect for ODBC SQL Server driver
URL Namesubsequent-executions-of-a-stored-procedure-fail-with-no-error-message-with-connect-for-odbc-sql-server-driver
Article Number000117745
EnvironmentProduct: Connect for ODBC SQL Server Driver
Version: 7.1
O/S: Linux x64
Database: SQL Server
Application: N/A
Question/Problem Description
Subsequent executions of a stored procedure fail with no error message with Connect for ODBC SQL Server driver
Steps to Reproduce
Clarifying Information
Error Message
Defect Number73505
Enhancement Number
Cause
The driver was changing the IPD after the initial execution of the store procedure.
Resolution
Fixed in hotfix 07.16.0355

Refer to "Connect and Connect64 for ODBC hot fix download and install instructions" for instructions on how to download and install the hot fix.
Workaround
Set the following connection option. If your WorkArounds option already contains a value, add this value to it:

WorkArounds=536870912

This option allows re-binding of parameters after calling SQLExecute for prepared statements.
Notes
Last Modified Date7/26/2017 1:59 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.