>>>>So what happens if you remove the xsd part with an editor? If this solves the problem you might do this using string operations or the like.
>>>>
>>>>If not, you might be unable to solve the problem with VFP internal commands
>>>
>>>I cannot remove the xsd part from the xml (it is used by too many customers). Then I will look for a different approach.
>>
>>Why not? Simply create a copy to some temp and manipulate the snapshot. Just to test if you can use it at all.
>
>Testing it on my computer works. But it is a too big of a maintenance headache to implement. Different customers have all the EmailList.xsd in their XML files. But the XML files are of different "structure". Up to now, this XML was used only by .NET application which works well since it ignores the XSD part.
>Now I need to access the same XML from the VFP and running into the problem with the XSD.

If it works on your comp, why not on any other comp? You need to find the reason, not the symptom.

How, w/o a XSD, do you think VFP can determine a complex datastructure of a XML? Guesswork?