That is the answer it appears. I suspected the same thing when I realised that it didn't work even with the xml string in memory.

However, I think this must be a bug because the directory containing the xml files is in the VFP path, and according to the help file, that's supposed to work.

I guess I should report it.

Thanks again Sergey.

Alan

>>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.
>>
>>Very strange.
>
>Alan,
>
>Maybe it cannot fine your external schema? Try inline schema

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