DOCUMENT:Q173513 27-AUG-1999 [odbc] TITLE :BUG: Open/Close CRecordset Repeatedly Results in AV PRODUCT :Open Database Connectivity (ODBC) PROD/VER:WINDOWS:3.0 OPER/SYS: KEYWORDS:kbprogramming ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Open Database Connectivity, version 3.0 ------------------------------------------------------------------------------- BUG #: 4797 (NT: ODBC30) SYMPTOMS ======== An ODBC application may get an access violation (AV) using the ODBC cursor library (Odbccr32.dll) if both of the following conditions are true: - It creates more than one CRecordset objects. -and- - The following operations are done repeatedly on the CRecordset objects: Open, MoveLast or Requery and Close. The access violation error happens when the application tries to use the Close method of CRecordset or invoke the SQLFreeStmt ODBC function. STATUS ====== Microsoft has confirmed this to be a problem in Open Database Connectivity version 3.0. This problem has been corrected in Open Database Connectivity version 3.5. Additional query words: gpf general protection fault ====================================================================== Keywords : kbprogramming Technology : kbAudDeveloper kbODBCSearch kbODBC300 Version : WINDOWS:3.0 Issue type : kbbug Solution Type : kbpending ============================================================================= 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. Copyright Microsoft Corporation 1999.