>>Does XMLToCursor have field length limitations? I am using XMLToCursor to bring in data exported by SQL Server to XML format. The field that comes from an Image field in SQL Server gets to the XML fine, but is corrupted in the table created by XMLToCursor.
>
>Some nonprintable characters are treated as XML special characters and are not imported. In my practice this is the reason for crashing the data.

That could be it. We faced that situation also but it was with a standard memo field. However, the same pattern may apply here. That's why using the new attachment ability is now the way to go with the SOAP 3 toolkit in order to avoid those exceptions.