Thanks Sergey, but I do have SP4 installed.

I discovered late yesterday that the problem only occurs if I have to use the path. According to the help, this should work, but I found that if I make the directory containing the xml file the current directory, and do not include the path with the file name, then it works fine. I should point out that this is happening at work on a Win2k OS. I haven't had time to test it at home on my XP machine.

I don't know if this is a bug in the dll or not. Can you confirm that using the path works for you? The output works even using the path, but not the import.

Oddly enough, even if I import the xml file using FileToStr() and then use XMLToCursor on the memory variable (dropping the 512 flag), I get the same 'cannot locate' error if the current directory is not the one containing the xml file. I suppose that must mean that it's the 'xsd' file that is causing the problem.

Very strange.

Alan

>Hi Alan,
>
>The XMLTOCURSOR() function internally uses MSXML 3.0. The message may indicate that there's a problem with MSXML 3.0 on that PC. I would try to upgrade to the latest SP http://www.microsoft.com/downloads/details.aspx?familyid=c0f86022-2d4c-4162-8fb8-66bfc12f32b0&languageid=f49e8428-7071-4979-8a67-3cffcb0c2524&displaylang=en
>
>>Using VFP8, I can take a dbf and write it out to xml using, for instance,
>>

CURSORTOXML('cl_claim','mcout\claims.xml',1,526,0,'claims.xsd')

>>
>>But if I try to get it back into a cursor with
>>

XMLTOCURSOR("mcout\claims.xml","xmlclaims",516)

>>
>>I get an error:
>>

MSXML3.DLL: The system cannot locate the object specified

>>Anyone have any idea what might be going on here?
>>
>>Thanks
>>
>>Alan