Microsoft KB Archive/318977

= FIX: The CDATA Section of CURSORTOXML May Format Characters Incorrectly =

Article ID: 318977

Article Last Modified on 3/27/2002

-

APPLIES TO


 * Microsoft Visual FoxPro 7.0 Professional Edition

-



This article was previously published under Q318977



SYMPTOMS
When the nFlag parameter is set to 8 in the CURSORTOXML function in a memo field, the following characters may be formatted incorrectly:
 * less than (<)
 * greater than (>)
 * ampersand (&)



RESOLUTION
To resolve this problem, obtain the latest service pack for Visual FoxPro for Windows 7.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

316964 How to Obtain the Latest Visual FoxPro for Windows 7.0 Service Pack



STATUS
Microsoft has confirmed that this is a problem in Microsoft Visual FoxPro for Windows 7.0.

This problem was first corrected in Visual FoxPro for Windows 7.0 Service Pack 1.



MORE INFORMATION
When you set the nFlag parameter to 8 in the CURSORTOXML function, the contents of the memo field with an XML CDATA section wrap. This protects the data if the <, >, or & characters are used in the memo field. These characters are not formatted correctly in the memo field when the CURSORTOXML function is used in the original release version of Visual FoxPro 7.0.

Steps to Reproduce Behavior
Paste the following code into a program file, and then run the file from the Command window: CLEAR CREATE CURSOR myxml_memo (fld_memo M) APPEND BLANK REPLACE fld_memo WITH &quot;Joe & Jim's last name is .&quot; CURSORTOXML(&quot;myxml_memo&quot;, &quot;myxml_var1&quot;, 1, 8)

? myxml_var1 myxml_var2 = STRTRAN(myxml_var1, &quot;&&quot; + &quot;amp;&quot;, &quot;&&quot;) myxml_var2 = STRTRAN(myxml_var2, &quot;&&quot; + &quot;lt;&quot;, &quot;<&quot;) myxml_var2 = STRTRAN(myxml_var2, &quot;&&quot; + &quot;gt;&quot;, &quot;>&quot;)
 * Displays CDATA section with the &amp, &lt, and &gt substitutions.
 * !* Note: the strings in the code are broken up for clarity.
 * !* You can write them as one literal in your code.

? myxml_var2 LOCAL ox AS MSXML2.DomDocument.3.0 ox = NEWOBJECT(&quot;MSXML2.DomDocument.3.0&quot;) ox.Async = .F. ox.LoadXML(myxml_var1) ? ox.DocumentElement.FirstChild.FirstChild.Xml ? ox.DocumentElement.FirstChild.FirstChild.Text ? &quot;&quot; ox.LoadXML(myxml_var2) ? ox.DocumentElement.FirstChild.FirstChild.Xml ? ox.DocumentElement.FirstChild.FirstChild.Text
 * The CDATA section should resemble the following:
 * This is displayed incorrectly in the MSXML text.
 * This is expected when you use CDATA to wrap the text.

Keywords: kbbug kbfix kbvfp700sp1fix kbcodesnippet kbctrl KB318977

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.