According to KB#315580 any characters below ASCII 32 (other than 9,10, and 13) will cause the "An Invalid character was found in text content". Does anyone have any suggestions for trapping for the existence of these characters so that XMLtoCursor will not fail? Or am I left to catch this error, call a routine to strip all such characters and then issue the XMLtoCursor again? In doing it this way, I am thinking I have to check for each (1-32 exect 9,10 and 13) or is there some other way to strip out?

Thanks in advance for any suggestions


>I set the nFlags to 8 but still not having any luck in XMLtoCursor parsing. Error is still generated. My code is as follows:
>Cursortoxml('myDailyChanges','lcPacket',1,8,0,'1','','dailyPacket')
>
>Any thing incorrect on above?
>
>
>>
>>Use nFlags = 8 to wrap the memo fields with a CDATA marker in the XML. This also needs to be done if the data contains special characters like <.
>>
>>>Working with XMLtoCursor and CursorToXML I have found the following error occurs for us. Investigating discovered that we have memo fields in our tables with unrecognizable characters. For example, the user was attempting to enter a capital 'L' and mistakenly hit the Control-L instead. The memo field stored the ascii 12 character rather than the 'L'. When using the CursorToXML function all works okay, however when using XMLtoCursor the error occurs.
>>>
>>>How does one trap for this for all instances where the control key would be used by error rather than the Shift key in data entry on an editbox?