Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Installing MSXML v3.0
Message
From
01/04/2002 11:19:47
James Blackburn
Qualty Design Systems, Inc.
Kuna, Idaho, United States
 
 
To
29/03/2002 20:20:00
General information
Forum:
Visual FoxPro
Category:
InstallShield
Miscellaneous
Thread ID:
00639086
Message ID:
00639472
Views:
29
Thanks Marcia

I am using xmltocursor and it is getting an error on my customers machine. The main question is why InstallShield is not installin msxml v3 when I have the MSXML 3 msm file checked to distribute?

>Hi James.
>
>Also, how can I tell what version is installed?
>
>You may have several versions installed but this is an entirely different issue from which version of the dll will be used when you instantiate the dom < s >. If you use the old syntax like this:
>
>
>oParser = CREATEOBJECT( 'Microsoft.XmlDom' )
>
>
>It is going to use MSXML.DLL not matter what else is installed on your system. If you use the version independent progid, like this:
>
>
>oParser = CREATEOBJECT( 'MsXml2.DomDocument' )
>
>
>you'll have to take a look at the registry to be sure which version of MSXML is being used. On my system, if I look up the different clsids under HKCR\CLSID, this is what I get:
>
>
>clsid                                  ProgID                dll
>{2933BF90-7B36-11d2-B20E-00C04F983E60} MicroSoft.XmlDom       MsXml.dll
>{F6D90F11-9C73-11D3-B32E-00C04F990BB4} MsXml2.DomDocument     MsXml3.dll
>{f5078f1B-c551-11d3-89b9-0000f81fe221} MsXml2.DomDocument.2.6 MsXml2.dll
>{f5078f32-c551-11d3-89b9-0000f81fe221} MsXml2.DomDocument.3.0 MsXml3.dll
>{88d969c0-f192-11d4-a65f-0040963251e5} MsXml2.DomDocument.4.0 MxXml4.dll
>
>
>HTH
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform