Microsoft Provides Workaround for Row-Retrieval Problem

Microsoft has provided a workaround for a problem that occurs when you retrieve rows from a SQL Server 2000 database by using browse mode in a client application. If you retrieve rows from a SQL Server database by using browse mode in a client application and the rows contain null values, you might 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 the SQL Server program returns, the rows aren't correctly updated in the SQL Server database. This problem occurs when 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, and the table's unique key index key columns accept null values. To work around this problem, create the table on the inner side of a query's outer join statement so that the table's unique index key columns can' accept null values. To find out more, read the Microsoft article "You may not be able to identify or modify rows after you retrieve the rows from SQL Server 2000 by using browse mode" at
   http://support.microsoft.com/?kbid=886834

Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish