The information in this article applies to:
SYMPTOMSThe DBLIBRARY call dbclropt results in the message SUCCEED, but row buffering is not disabled on the DBPROCESS. Continued dbnextrow calls can cause unexpected results, including a general protection (GP) fault of the client application. CAUSEThe dbclropt function correctly resets the option, so that when dbisopt is called it will return true; however the dbclropt does not reset the buffer size to zero. Therefore, functions like dbnextrow continue buffering. WORKAROUND
Use the SQL Server 6.5 version of DBLIBRARY, or close and re-open the
connection.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server for
Windows version 6.0. We are researching this problem and will post new
information here in the Microsoft Knowledge Base as it becomes available.
Keywords : kbbug6.00 |
Last Reviewed: March 26, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |