Microsoft KB Archive/818962

= FIX: Data Loss Occurs When You Deserialize a Serialized Dataset When Column Names Contain a Colon Character =

Article ID: 818962

Article Last Modified on 10/25/2005

-

APPLIES TO


 * Microsoft .NET Framework 1.1

-





SYMPTOMS
When you deserialize a serialized dataset where one or more column names contains a colon character, you lose data. For those column names that contain a colon, DBNULL is returned as column data.



RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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. The English version of this fix has the file attributes (or later) 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 tool in Control Panel.   Date         Time    Version     Size     File name     Platform 19-Apr-2003 03:00  1.1.4322.902    1,290,240  System.data.dll This fix is for .NET Framework 1.1.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

