Microsoft KB Archive/151600

{|
 * width="100%"|

BUG: Dbclropt Does Not Reset the DBBUFFER Status

 * }

Q151600

-

The information in this article applies to:


 * Microsoft SQL Server version 6.0

-

SYMPTOMS
The 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.

CAUSE
The 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.

Attempts to call dbsetopt for DBBUFFER with 0 simply sets the buffer value to 100, as documented in the options section of Books Online.

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.

This problem does not occur in Microsoft SQL Server version 6.5.

Keywords :

Issue type :

Technology : kbSQLServSearch kbAudDeveloper kbSQLServ600