>>How do I found out the server name and class of *any* registered automation server?
>>
>>For example, I have two versions of XMLDOM registered: MSXML.DLL and MSXML3.DLL. WWXML only finds the OLDER (and buggy) one when it executes CREATEOBJECT("Microsoft.xmldom"). I have found I can use Microsoft's XMLINST.EXE to change all the classids, but this may corrupt a prior program that expects the older classid.
>
>Locate the ProgID of the server in HKEY_CLASSES_ROOT; it will contain the CLSID of the class. Locate the CLSID in HKEY_CLASSES_ROOT, and there will be either an InProcServer32 entry or a LocalServer32 entry identifying the file containg the control or class.
To find out what the new ProgID is (e.g. "server.class"), I searched the registry for the MSXML3.DLL name and found a bunch of them. I finally found "MSXML2.DOMDocument" (which triggered in my mind because I think I saw it recently), and it seems to be the newer version of "Microsoft.XMLDom".
Am I missing something, or did Microsoft decide to change the server and classname to something completely different? Wouldn't it make sense to have "MXSML.DOMDocument", and then "MSXML2.DOMDocument" or something along those lines?
Scott McDaniel
MCP VFP Desktop