You may not be able to identify or modify rows after you retrieve the rows from SQL Server 2000 by using browse mode (886834)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
SYMPTOMSIf you retrieve rows from a Microsoft SQL Server database by using browse mode in a client application and the rows contain null values, you may not be able to identify the appropriate rows and perform the correct manipulations to the rows in the result set. Additionally, when you try to update the rows by using the additional key column metadata that is returned by the SQL Server program, the rows are not correctly updated in the SQL Server database. This problem occurs when all the following conditions are true: - The SELECT query that you try to use to retrieve the rows from the SQL Server database involves an outer join operation.
- A unique index is defined on the table on the inner side of the outer join statement.
- The unique index key columns of the table can accept null values.
WORKAROUNDTo work around this problem, create the table on the inner side of an outer join statement of the query so that the unique index key columns of the table cannot accept null values.REFERENCESFor more information about browse mode, see the "SELECT" topic and the "BrowseMode" topic in SQL Server Books Online.
For additional information about the same problem in Microsoft SQL Server 2005, click the following article number to view the article in the Microsoft Knowledge Base:
885146
Additional information about the FOR BROWSE option and the NO_BROWSETABLE option in SQL Server 2005
Modification Type: | Major | Last Reviewed: | 10/19/2004 |
---|
Keywords: | kbupdateissue kbtable kbTSQL kbtshoot kbprb KB886834 kbAudDeveloper |
---|
|