FIX: MSPersist does not handle special characters such as carriage returns or line feed correctly (329791)


The information in this article applies to:

  • Microsoft Data Access Components 2.7
  • Microsoft Data Access Components 2.7 SP1
This article was previously published under Q329791

SYMPTOMS

When you try to fetch data that contains special characters such as carriage returns or line feed by using Microsoft ADO and the Microsoft Data Access OLE DB Persistence Provider (MSPersist), users may receive the following error message:
Run-time error '-2147467259 (80004005)': An invalid character was found in text content.

CAUSE

This behavior occurs because Microsoft Data Access OLE DB Persistence Provider (MSPersist) invokes Microsoft XML Parser (MSXML) 3.0 in Microsoft Data Access Components (MDAC) 2.7. MSPersist invokes MSXML 2.6 in MDAC 2.6. MSXML 3.0 enforces the XML spec wherein it does not permit characters below 0x20H, with some exceptions.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Microsoft Data Access Components (MDAC) 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 hotfix 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
   --------------------------------------------------------------
   09-Oct-2002  23:56  2.71.9031.7       180,224  Msdaprst.dll

WORKAROUND

There is no workaround.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

MORE INFORMATION

When you use Microsoft SQL Server 2000 Analysis Services together with the Microsoft OLAP Provider by using the drillthrough functionality, the record that contains the special characters is not displayed. No errors or warnings are displayed.

Steps to reproduce the behavior

  1. Start a new standard .exe project in Microsoft Visual Basic. By default, that is named Form1 is created.
  2. Add a CommandButton control to Form1.
  3. Paste the following code in the General Declarations section of Form1:
    Private Sub Command1_Click()
Dim rs As Object
Set rs = CreateObject("ADODB.Recordset")

With rs
    .Fields.Append "Test", 201, 256
    .Open
    .AddNew
    .Fields("Test").Value = "Some Value 1"
    .AddNew
    .Fields("Test").Value = "Some Value 2"
    .AddNew
    .Fields("Test").Value = Chr(12) 'Inserting the special character here.
    .Save "C:\MyFileName.txt", 1
    .Close
End With

Set rs = Nothing
Set rs = CreateObject("ADODB.Recordset")
rs.Open "C:\MyFileName.txt"
rs.MoveFirst
For i = 1 To 3
    Debug.Print rs.Fields(0).Value
    rs.MoveNext  'Will Error on the third record
Next i
rs.Close
End Sub
  4. Run the application. Notice that you receive the error message that is mentioned in the "Symptoms" section.
Modification Type:MinorLast Reviewed:10/11/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix KB329791 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.