>After the call has been done to a method, from my Web Service, I am using this to convert the XML string to a cursor:
>
>

>XMLTOCURSOR(lcXML,'Temp')
>

>
>But, this has caused a fatal error overnight. The Visual FoxPro error handler didn't kick in. The C05 error took over.
>
>Did is due to a change on the provider where the method failed to return the proper data. However, this shouldn't react like this. Any comment?

I don't know if you saw my post some hours ago but for me this line..
= XMLTOCURSOR(cFileName, "TmpXMLCursor", 512)
... is causing an 'OLE error code 0x800401f3: Invalid class string' error on some systems (VFP7 / W2K SP2). In the Knowledge Base / VFP7 Help system this error code is documented in terms of a call to CREATEOBJECTEX(), which does not appear in my code.

Presumably XMLTOCURSOR makes use of a particular one of the XML services DLLs that may exist side-by-side in the WinSys folder - MSXML.DLL, MSXML2.DLL, MSXML3.DLL, MSXML4.DLL etc. I wonder if it is possible to force the use of the most recent one?? Would direct calls to a MSXML2.DOMDocument (+ wrapper code) be a safer way to go??

John Burton