The information in this article applies to:
SYMPTOMSWhen deleting a record in the data-bound Apex Grid Control (DBGRID32.OCX), the following error appears in a message box: The actual cursor name may vary, so instead of "SQL_CUR12522868X," you may see "SQL_CURXXXXXXXXX" where the X can be any value. CAUSEThis is a problem in the Apex Grid control. RESOLUTION
To work around the problem, set the CursorDriver property of the Remote
Data Control (RDC) to one of the following:
STATUSMicrosoft has confirmed this to be a problem the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATIONThe Apex Grid Control issues positioned deletes of the form:
Most ODBC drivers need the cursor library to support such statements. If
the CursorDriver property is set to 0, the cursor library does not get
loaded and the positioned delete statement causes the error mentioned
above. Setting this property to 1 (ODBC Cursors) forces the cursor library
to be used.Setting CursorDriver to 2 (Server-side cursors) causes the Apex Grid control to delete records using keyset cursors (SQLSetPos) and the problem is resolved. Additional query words: 4.20 kbdsd DBGRID
Keywords : kbVC kbx86 PrgCtrlsCus |
Last Reviewed: July 28, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |