Was not aware of that. so you are saying that if the memo field is a memo binary that the XML's will not choke? Thanks for the tip, will look into it. Right now, i am doing a strip of all ascii values < 32 except 9,10, and 13 and getting by with that.



>>Working with XML and I have come across a CHR(19) in some memo fields. This errors out when trying to to the XMLTOCURSOR because of illegal character.
>>
>>I am trying to figure out what the user did to get this CHR(19) entered? What key strokes would create it?
>
>Don't even try to catch that. There could be any number of special characters, some of them with quite legitimate reasons. Just set your memos to NOCPTRAN (i.e. memo, binary), and then the created xml will have the content wrapped in base64 encoding. Not a line of code to write :).