BUG: ODBC: SQLGetProp Causes IC Error in Debug Window

Last reviewed: April 25, 1997
Article ID: Q148330
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, versions 3.0, 3.0b

SYMPTOMS

An internal consistency (IC) error occurs when you attempt to view the properties of a connection using SQLGetProp in the DEBUG window.

CAUSE

You are using an invalid connection handle in the SQLGetProp() function in the DEBUG window.

WORKAROUND

Print the return value of SQLGetProp() to the desktop or currently active window using ? or \ printing as in this example:

   ? SQLGETPROP(<handle>, "BATCHMODE")

In this example, <handle> is a valid handle to the connection.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Problem

  1. Create an ODBC data source based on the Oracle 7.0 driver.

  2. Create a database with a remote view based on the data source created in step 1.

  3. Open the remote view.

  4. Open the Debug window, and type the following line in the left pane:

          SQLGetProp(3, "BATCHMODE")
    

    In this example, 3 is an invalid connection handle.


Additional query words: 3.00 3.00b ICE
Keywords : buglist3.00 buglist3.00b FxinteropOdbc vfoxwin vfpbug5.0a kbbuglist
Version : 3.00 3.00b
Platform : WINDOWS
Issue type : kbbug


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 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.