FIX: SQLSetCursorName Fails When "Use ANSI Quoted Identifiers" Is Cleared

This article was previously published under Q262519
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56244 (SQLBUG_70)
SYMPTOMS
When you try to use a data source name (DSN) entry that does not have the Use ANSI Quoted Identifiers option selected to try to set a cursor name (through the use of the SQLSetCursorName API), the following error message appears:
"[Microsoft][ODBC SQL Server Driver]Invalid Cursor Name"
To work around this problem, select the Use ANSI Quoted Identifiers option in the DSN. For additional information on ODBC, please refer to the platform SDK and MSDN documentation.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 7.0. For information about how to download and install the latest SQL Server Service Pack, see the following Microsoft Web site: For more information, contact your primary support provider.
MORE INFORMATION

Steps to Reproduce the Behavior in 32-bit ODBC Test (Odbcte32.exe)

  1. Create a DSN to connect to Microsoft SQL Server.
  2. Clear the Use Ansi Quoted Identifiers option in the DSN.
  3. Within ODBC Test, select Full Connect and choose the DSN that you modified in step 2.
  4. From the Stmt menu, choose SQLSetCursorName. In the SQLSetCursorName dialog box, specify any cursor name (such as "Cl").
  5. Click ok. The error message will appear.
Properties

Article ID: 262519 - Last Review: 01/10/2015 12:35:13 - Revision: 2.3

  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft Open Database Connectivity 2.1
  • Microsoft ODBC Driver for Microsoft SQL Server 3.7
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB262519
Feedback