Feedback
Did this article resolve your question/issue?

   

Article

SQLDescribeParam() on a Stored Procedure call fails when the SP exists in a different database.

Information

 
TitleSQLDescribeParam() on a Stored Procedure call fails when the SP exists in a different database.
URL NameSQLDescribeParam-failed-after-upgraded-to-7-1-5-when-the-SP-exist-in-a-different-database
Article Number000152693
EnvironmentProduct: Connect for ODBC SQL Server Wire Protocol driver.
Version: 07.16.0294 (B0305, U0205)
OS: Linux
Database: SQL Server
Application: All supported applications
Question/Problem Description
SQLDescribeParam() fails on a Stored Procedure fails when the SP exists in a different database.
Steps to Reproduce
Clarifying Information
Error Message[DataDirect][ODBC SQL Server Wire Protocol driver]Invalid Object Name
Defect NumberDefect 51684
Enhancement Number
Cause
Resolution
Fixed in hot fix 07.16.0305 (B0316, U0209)

ODBC :
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
Use the Connect for ODBC Legacy driver
Notes
Last Modified Date11/20/2020 7:21 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.