Feedback
Did this article resolve your question/issue?

   

Article

Print statements inside stored procedures are not returned in proper sequence using the Connect for SQL Server driver.

Information

 
TitlePrint statements inside stored procedures are not returned in proper sequence using the Connect for SQL Server driver.
URL NamePrint-statements-inside-Stored-procedure-not-coming-in-proper-sequence
Article Number000182399
EnvironmentProduct: Connect/Connect64 for ODBC SQL Server WP driver
Version: 6.1
OS: AIX
Database: SQL Server
Application: All supported applications
Question/Problem Description
Print statements inside stored procedures are not returned in proper sequence using the Connect for SQL Server driver.
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
The InstallDir property in the [ODBC] section of the odbc.ini file doesn't point to the correct location.
Resolution
Correct the InstallDir property in the odbc.ini file to the correct location.
Workaround
Notes
Last Modified Date2/3/2016 9:06 AM
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.