FIX: Distributed Query with NO_BROWSETABLE Against Timestamp Column Can Cause Access Violation

Article translations Article translations
Article ID: 268153 - View products that this article applies to.
This article was previously published under Q268153
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 58068 (SQLBUG_70)
Expand all | Collapse all


If NO_BROWSETABLE is set ON, a distributed query against a table with a timestamp column can result in a handled EXCEPTION_ACCESS_VIOLATION.


Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.


The access violation occurs on the local SQL Server that initiated the query to the remote server. NO_BROWSETABLE is typically only used by applications that use certain types of result processing, such as disconnected recordsets.


Article ID: 268153 - Last Review: February 28, 2014 - Revision: 5.0
  • Microsoft SQL Server 7.0 Service Pack 2
kbnosurvey kbarchive kbbug kbfix kbqfe KB268153

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from