BUG: dbrettype Return Values Differ from Documentation

Last reviewed: April 29, 1997
Article ID: Q113852

The information in this article applies to:
  • Microsoft SQL Server Programmer's Toolkit, version 4.2
BUG# 9965 (4.2)

SYMPTOMS

Calling dbrettype() to retrieve the type of a remote procedure return parameter returns a token value indicating a nullable datatype instead of a token value indicating the length of the datatype, as indicated in the SQL Server Programmer's Toolkit documentation.

CAUSE

When issuing RPC requests from a DB-Library (DB-Lib) application to an ODS server, the return parameter types returned by dbrettype() will be identified as a nullable datatype instead of a datatype identifying the length of the return parameter.

For example, SQLINTN will be returned instead of SQLINT4. The return value from dbrettype() will identify the length of the return parameter if the RPC is issued against a SQL Server. This behavior occurs when using DB- Library 4.20.21 and later.

WORKAROUND

In order to determine the datatype of the return parameter, use the value returned by dbrettype() in conjunction with the parameter length returned by dbretlen().

STATUS

Microsoft has confirmed this to be a problem in DB-Library version 4.20.21. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: open data services gateway proc dblib
Keywords : kbprg SSrvDB_Lib SSrvProg
Version : 4.2.21 | 4.2.21 | 4.2.21
Platform : MS-DOS OS/2 WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.