Tom

Thanks for replying. You've answered one thing I wanted to know, namely that it is MSXML3 that is implicitly called. The machine (W2K SP2) is at a client's site in another country. I can only diagnose via email at the moment, e.g. by retrieving system diagnostics that my app writes.

I asked them to install MSXML4 but of course that would have no effect given what you say. I have already been testing (on my machine) a wrapper based on
oXMLDoc = CREATEOBJECT("MSXML2.DOMDocument.4.0")
along the lines you suggested (it works perfectly well) and will deploy this if all else fails.

In my distribution (Installshield Express) build I am not currently including the MSXML3.MSM module, but from what you say I should do to ensure it's on the target PC.

The browser they are using is IE 5.00.2920. Since they are using W2K SP2 I had assumed that this would have upgraded any components that were faulty in the original releases of W2K and IE that relate to XML. But perhaps this is not correct. I can get easily them to either put on IE5.5 or IE6 or the latest MSXML3.

John Burton

>Interesting. Installing the latest MSXML3 on the client machine didn't help?
>
>Try going to the client machine and executing this line:
>

x = CREATEOBJECT("msxml2.domdocument.3.0")

>This is the interface that VFP7 uses when you call XMLTOCURSOR(). If you get an error here, then the machine doesn't have msxml3 correctly installed.
>
>If you don't get an error, try this:
>

    x.load("Your_xml_file.xml")  && Use the name of your XML file.
>    ? x.firstChild.nextSibling.firstChild.xml

>Do you see a portion of your XML data?
>
>If you receive any error messages, then something is wrong with the MSXML installation, and you should try the MSXML3 SP2 installation again. If you don't see any data, then perhaps there is a problem in your XML file?
>
>If you do see data, please let me know, as I will want to investigate this further. :)
>
>-Tom
>
>[This post is provided "AS-IS" with no warranties, and confers no rights.]