FIX: You receive an error message when a Visual Basic application opens a dynamic cursor on a GROUP BY query in SQL Server 2000 Service Pack 4 (910710)


The information in this article applies to:

  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Standard Edition
BUG #: 20000192 (SQL Server 8.0)
Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by the hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart the computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package

SYMPTOMS

When a Microsoft Visual Basic application opens a dynamic cursor on a GROUP BY query, you receive an error message that is similar to the following:
Run-time error '3251': Object or provider is not capable of performing requested operation
This problem occurs when the following conditions are true:
  • The server is running Microsoft SQL Server 2000 Service Pack 4 (SP4).
  • The recordset object is declared by using the WithEvents keyword.
  • The dynamic cursor is implemented on the server.
For a list of all publicly released SQL Server 2000 post-Service Pack 4 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

894905 Cumulative list of the hotfixes that are available for SQL Server 2000 SP4

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

  • SQL Server 2000 SP4

    For more information about how to obtain SQL Server 2000 SP4, click the following article number to view the article in the Microsoft Knowledge Base:

    290211 How to obtain the latest SQL Server 2000 service pack

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.SQL Server 2000, 32-bit hotfix
File nameFile versionFile sizeDateTimePlatform
Dtsui.dll2000.80.2172.01,593,34410-Nov-200506:42x86
Impprov.dll2000.80.2172.0102,40010-Nov-200506:42x86
Mssdi98.dll8.11.50523.0239,10406-Jun-200522:46x86
Ntwdblib.dll2000.80.2172.0290,81610-Nov-200506:42x86
Odsole70.dll2000.80.2172.069,63210-Nov-200506:42x86
Osql.exe2000.80.2039.057,34404-May-200504:32x86
Pfclnt80.dll2000.80.2172.0430,08010-Nov-200506:42x86
Replprov.dll2000.80.2172.0237,56810-Nov-200506:42x86
Semexec.dll2000.80.2172.0856,06410-Nov-200506:42x86
Sqlagent.exe2000.80.2172.0323,58410-Nov-200505:17x86
Sqldiag.exe2000.80.2172.0118,78410-Nov-200505:49x86
Sqldmo.dll2000.80.2172.04,362,24010-Nov-200506:42x86
Sqlfth75.dll2000.80.2172.0102,40010-Nov-200505:18x86
Sqlservr.exe2000.80.2172.09,158,65610-Nov-200506:42x86
Sqlsort.dll2000.80.2172.0589,82410-Nov-200506:42x86
Stardds.dll2000.80.2172.0176,12810-Nov-200506:42x86
Svrnetcn.dll2000.80.2172.0110,59210-Nov-200506:42x86
Ums.dll2000.80.2172.035,84010-Nov-200506:42x86
SQL Server 2000, 64-bit hotfix for Itanium processors
File nameFile versionFile sizeDateTimePlatform
Impprov.dll2000.80.2172.0244,73611-Nov-200501:34IA-64
Mssdi98.dll8.11.50523.0758,78411-Nov-200501:34IA-64
Msvcr71.dll7.10.3052.4348,16011-Nov-200501:34x86
Odsole70.dll2000.80.2172.0150,52811-Nov-200501:34IA-64
Pfclnt80.dll2000.80.2172.01,187,84011-Nov-200501:34IA-64
Replprov.dll2000.80.2172.0538,62411-Nov-200501:34IA-64
Replprov2.dll2000.80.2172.0538,62411-Nov-200501:34IA-64
Sqlagent.exe2000.80.2172.01,061,37611-Nov-200501:34IA-64
Sqldiag.exe2000.80.2172.0334,33611-Nov-200501:34IA-64
Sqldmo.dll2000.80.2172.013,860,35211-Nov-200501:34IA-64
Sqlfth75.dll2000.80.2172.0246,78411-Nov-200501:34IA-64
Sqlservr.exe2000.80.2172.024,924,67211-Nov-200501:34IA-64
Sqlsort.dll2000.80.2172.0617,47211-Nov-200501:34IA-64
Sqlsort_.dll2000.80.2172.0617,47211-Nov-200501:34IA-64
Sqlsort_1.dll2000.80.2172.0617,47211-Nov-200501:34IA-64
Svrnetcn.dll2000.80.2172.0427,52011-Nov-200501:34IA-64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Steps to reproduce the problem

To reproduce the problem, use the following Visual Basic code example. 
Dim cnx As New ADODB.Connection
    Dim srvName As String
    
    srvName = "myServer"
    cnx.ConnectionString = "Provider=SQLOLEDB;Data Source=" & srvName & ";Integrated Security=SSPI;Initial Catalog=Northwind"
    cnx.Open
    
    Dim cmd As New ADODB.Command
    Set cmd.ActiveConnection = cnx
    
    cmd.CommandText = "SELECT Customers.CustomerID, Orders.OrderID FROM Customers LEFT OUTER JOIN Orders ON Customers.CustomerID = Orders.CustomerID GROUP BY Customers.CustomerID, Orders.OrderID ORDER BY Orders.OrderID"
    cmd.CommandType = adCmdText
    'cmd.CommandText = "dbo.test"
    'cmd.CommandType = adCmdStoredProc
    
    Set rs = New ADODB.Recordset
    rs.CursorLocation = adUseServer
    
    ' should fail with 3251
    rs.Open Source:=cmd, CursorType:=adOpenDynamic, LockType:=adLockOptimistic, Options:=1
        
    rs.Close
    Set rs = Nothing
    Set cmd = Nothing
    
    cnx.Close
    Set cnx = Nothing
Note In this code example, change the value of the srvName parameter to the name of the server.
Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbBug kbfix kbtshoot kbHotfixServer kbQFE kbpubtypekc KB910710 kbAudITPRO kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.