I've got a situation where I'm reading some complicated XML sent to me from an external source, breaking it apart, and processing it so that I get more manageable pieces of XML created via VFP's CURSORTOXML command. That's been working fine, but suddenly I'm having a problem. A number (1325300) was converted to "1E+6" - scientific notation. That number is higher than I can count, but it's just a piddling little number for VFP, so I wasn't sure why it was doing this. I did a little experimenting, but nothing helped. Since I occasionally run into strange problems that are solved by exiting VFP and restarting it, I tried that. Sure enough, I performed the import again and the number was processed correctly. Unfortunately, a number two fields down from the first one started getting screwed up (it had been fine up until now). It was only 114000 and some-odd, so VFP should not have had any problem, yet it was all asterisks. As mentioned, this had never happened before and on the production machine the same XML is processed without a hitch. I have a new development machine, so I'm wondering if I have a different version of MSXML - which CURSORTOXML depends on - and that version has caused CURSORTOXML to behave differently. Anyway, to get to the real point, any advice on this would be appreciated.

Russell Campbell