I will be looking at this more today. I know that in the XML sent to me, the values are correct. I have not looked to see if the values are incorrect in the VFP cursor I create from that XML. This is really the first opportunity I've had to look at this since posting the original message. But I'm wondering if VFP is taking the original XML and simply not making a field large enough. The reason would be that most of the values in this field are small - 5, 12, 46, 112 small. Then, for some reason, the value I've had trouble with is large (1325300). There's no reason for that, it's an identifier and they had been using an incrementing number so they were up into the hundreds, I think. Why this identifier is suddenly so large is beyond me, but I'm wondering if VFP is assigning the field size without consulting all values, then it turns out to be too small. Similar things can happen in an SQL statement.

Thanks for the reply.

>Can you trace that process through tracking the value to see where it becomes incorrect?