FIX:SQLDISCONNECT() May Cause Exception Error in Visual FoxPro

Last reviewed: October 29, 1997
Article ID: Q140613
3.00 WINDOWS kbprg kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft Visual FoxPro for Windows, version 3.0

SYMPTOMS

In Visual FoxPro 3.0, Using the SQLDISCONNECT() function sometimes causes Visual FoxPro to quit and display an "Exception error."

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was corrected in Visual FoxPro 3.0b for Windows.

MORE INFORMATION

Steps to Reproduce Problem

To reproduce this problem, a valid ODBC Data Source setup must be available on the system.

  1. In the Command window, type the following code:

    ?SQLSTRINGCONNECT()

  2. Click Cancel when the SQL Data Source dialog box appears or click OK if an 'Execution was canceled by user' dialog box appears.

  3. Type the following in the Command window:

    ?SQLCONNECT()

  4. Select a valid DataSource. You should receive a 1 for a connection handle.

  5. Type the following in the Command window:

    ?SQLDISCONNECT(1).

    Visual FoxPro quits with "Exception error" or "This program has performed an illegal operation and will be shut down."


Additional reference words: 3.00 fixlist3.0b buglist3.00
KBCategory: kbprg kbfixlist kbbuglist
KBSubcategory: FxprgClientsvr
Keywords : FxprgClientsvr kbbuglist kbfixlist kbprg
Version : 3.00
Platform : WINDOWS
Solution Type : kbfix


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