Knowledge Base

BUG: Call to SqlCursorFetch from Vbsql.vbx Causes GPF

Article ID: 163448

Article Last Modified on 10/16/2003


APPLIES TO


This article was previously published under Q163448
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.

Keywords: kbbug kbenv KB163448