Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)

Author  Topic 

Yak Posting Veteran

76 Posts

Posted - 2003-06-24 : 08:57:23

I'm doing a DB conversion for a company. There's a Delphi app that generates SQL code. (Don't start, I know). In the SQL Profiler I see SET NO_BROWSETABLE ON/OFF options come along. Does anyone know what this does?

Thnx... Jeroen.

Not Just a Number

15586 Posts

Posted - 2003-06-24 : 12:05:54
Don't think it's a SQL Server setting...not BOL, and doesn't get highlighted as a setting in QA...


Go to Top of Page

SQL Server MVP & SQLTeam MVY

846 Posts

Posted - 2003-06-24 : 13:39:52
Seems like this is something appended by ADO when you use a CursorLocation of adUseClient and a LockType of either adLockPessimistic,adLockOptimistic or adLockBatchOptimistic. There doesn't seem to be much info on this except a very old bit of info about RDS but I guess ADO is doing something similar

"SET NO_BROWSETABLE ON is an undocumented option performed for Remote Data Service (RDS) ActiveX Data Connector (ADC) connections to SQL Server. Enabling this option makes every SELECT statement act as though FOR BROWSE had been appended to the statement, but bypasses the temporary table that FOR BROWSE normally pipes the results through. The net effect is to add keys and timestamps to the query as hidden output columns so the client can update specific rows (updateable cursors) without separate trips to the server to pick up the metadata and using the query to get the appropriate columns."

Jasper Smith

Go to Top of Page

- Advertisement -