>Oddly, I found that the text in one of the source cursor row/columns contained a series of Chr(1) characters, and this is what seemed to be making it fail.
>
>All the "X" in this sample indicate the series of Chr(1) characters in the resulting output XML file, and that made it fail when read back in.
>
>

>_memberdata = 




































































































































































































































































































































































































































































































































XXXXXXXXXXXXXXXXXXXXXXX  <VFPData><memberdata name="cpartcountsource" display="cPartCountSource"/></VFPData>
>

>
>
>I have no idea where those characters came from in this _memberdata property of the form scx in the Code column, which is the text I had dumped to a cursor row.
>

Hi Matt!

It is the normal behaviour. When memberdata have more than 255 chars, VFP pads with 517 chr(0) characters at the left. I don't know why, and it is a strange behaviour, but it works that way. May be it is related to a design limitation or a workarround.

I discovered it while developing FoxBin2Prg and had to emulate it to generate a compatible binary.


Regards!