Reminder: you can download msxml6 from
http://www.microsoft.com/downloads/details.aspx?familyid=993c0bcf-3bcf-4009-be21-27e85e1857b1&displaylang=en

-- 
Regards,
- Umut Alev [MSFT]

This email sent from a machine running Vista RC1.


"Anthony Jones" <Ant@y...> wrote in message 
news:OxYgSW7vGHA.5056@T......
>
> "mikew" <mikew@d...> wrote in message
> news:1FADBC2A-9B85-4844-B2E0-F1D6E9D1D33B@m......
>> Sorry.  Yes windows server 2003.  The box has msxml, msxmlr, msxml2,
> msxml2r,
>> msxml3 and msxml3r in the winnt\system32 directory.  If I click on a .xml
>> file, it comes up in IE so I know an xml parser is installed.  But the vb
>> script interpreter for some reason is not seeing it.
>>
>> "Anthony Jones" wrote:
>
> Ok so you have MSXML3 hence this Prog ID should work:-
>
> Set oDOM = CreateObject("MSXML2.DOMDocument.3.0")
>
> this won't work:-
>
> Set oDOM = CreateObject("MSXML2.DOMDocument.6.0")
>
> unless you have msxml6.dll installed.
>
> So what ProgID are you using?
>
>>
>> >
>> > "mikew" <mikew@d...> wrote in message
>> > news:D6F6A79A-1072-4D9A-AD39-19BC367399EB@m......
>> > > I have written a VBScript the creates an XMLDOM object.  Works on my
>> > laptop.
>> > > But when I move it to the NT server, I get "Error creating object
> XMLDOM".
>> > > Server is running Windows 2006 and has IE 6.x.  I am told that XMLDOM
> is
>> > part
>> > > of Visual Studio 6.  Do I need to install MSXML6?  Will that give me
> the
>> > > XMLDOM dlls?
>> >
>> > What's windows 2006??  Do you mean XP or Windows 2003?
>> >
>> > What ProgIDs are you using?  MSXML6 is fairly new and will not be
> installed
>> > by any of the above.  MSXML3 is the most likely version you will have.
>> >
>> >
>> >
>> >
>
>