BUG: Call to SqlCursorFetch from Vbsql.vbx Causes GPF

 Last reviewed: April 10, 1997
Article ID: Q163448
The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5
BUG #: 16260 (Windows: 6.00 6.50)

SYMPTOMS

When you call SqlCursorFetch with "client side cursors" enabled, you will receive a general protection fault (GPF) in module Msdblib3.dll.

You can facilitate client side cursor usage by connecting to a 4.21a SQL Server, or setting the cursor option to client when connecting to a 6.0 or later SQL Server.

This problem occurs in both Visual Basic 3.0 and 4.0 environments.

WORKAROUND

To work around this problem, do either of the following:

  • Use a server side cursor.

    -or-

  • Use the 6.00.121 version of Msdblib3.dll. The 6.00.121 version was shipped with golden release of SQL Server 6.0. All newer versions of Msdblib3.dll exhibit the problem behavior.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.0 and 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words:
Keywords : kbbug6.00 kbbug6.50 kbenv SSrvGPF
Version : 6.0 6.5
Platform : 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 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.