>>That way you still pass a single string, and everything's in it. The cXml field would have to be a binary memo, AFAIK. I've done something like this for (believe it or not) backup.
>
>I like that approach. What is a "binary memo" compared to the usual kind?

That's the one where you add the "nocptrans" clause in the Create Table/Cursor command. Or you select memo(binary) in Modify Table.

Basically, tells VFP not to even try to convert its content based on codepage, but to take it as-is, byte for byte. In VFP7, when I was doing this, the memos would occasionally give me problems when reverting from xml to cursor unless they were binary. Probably builds the [Cdata...] thing as base64 instead of UTF-8 text or something like that. I've also done it in VFP8, and the cursor definition went something like

Create Cursor notes (eventpk i, sort1 c(30), sort2 c(30), ;
cDate c(25), ctitle c(120) NOCPTRANS, cArtist c(60) NOCPTRANS, ;
TYPE_FK I NOT NULL, ;

etc etc (no more memos there).