>>>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??
>>
>>I would say those are two different issues.
>
>You may be right. Nevertheless, neither is the first XMLTOCURSOR issue and it may be that SP1 did not (a) cure them all (b) make XMLTOCURSOR properly robust.
>
>J

AFAK, XMLTOCURSOR() function is not compatible with the latest versions (3 and 4, I believe) of MSXML.DLL. And all versions of MSXML.DLL should exist on PC because (again, AFAK), they do not inherit entirely or properly.