Consider the following scenario. In a Microsoft .NET Framework 2.0-based application, you bind the application to a data table. Next, you remove a column from the data table. Then, you try to use code to modify a record in this data table. In this scenario, the System.Data.Index.CompareRecords
method generates a System.NullReferenceException
This problem occurs if one of the following conditions is true:
- You remove a primary key from the data table.
- You remove a constraint collection from the data table.
- The AllowDBNull property for a column is set to "false," and you remove this column.
- The Unique property for a column is set to "true," and you remove this column.
This problem occurs because internal indexes reference the column that has been removed.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 2.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:Note
In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
You must install hotfix 916002 before you install this hotfix.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
FIX: Error message when you try to use the SqlClient class in an ADO.NET 2.0-based application to connect to an instance of SQL Server 2005: "New request is not allowed to start because it should come with valid transaction descriptor"
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone
tab in the Date and Time
item in Control Panel.
Collapse this tableExpand this table
|File name||File version||File size||Date||Time||Platform|
To work around this problem, create a new data table.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
After you apply this hotfix, you cannot remove a column when a DataView.RowFilter
property or a DataView.Sort
property references that column.
For more information about the System.NullReferenceException
exception, visit the following Microsoft website:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates