msxml.dll 1

[strongm]

Is anyone aware of any problems accessing and using the Microsoft XML Version 2 libraries from a VB application on Windows 95?

I don't have a 95 installation to test on, and a client is reporting that firstly the program wouldn't install properly if I included msxml.dll in the distribution, and secondly that the program won't run (ActiveX error 429 Can't Create Object when the program tries to create a New DOMDocument) if I don't include it.

Client says that his W95 machines all have at least IE5 installed, which should mean that the file version of mxxml.dll should be, at worst, 5.0.2919.6303.

 

[JustinEzequiel]

I am using Windows 95 and am using MS-XML with no problems

I have four versions of MSXML on my machine (am using both ver. 3 and ver. 4 right now)

Listing the DLL files in my system directory shows that the parser comes in a set of three DLLs

Try including the 'a' and 'r' files in your installation package

MSXML.DLL
MSXMLA.DLL
MSXMLR.DLL

msxml2.dll
msxml2a.dll
msxml2r.dll

msxml3.dll
msxml3a.dll
msxml3r.dll

msxml4.dll
msxml4a.dll
msxml4r.dll

 

[strongm]

Thanks for the feedback. Yep, I'm aware of all the different versions and have similar setup on my W98 test box (although I haven't put version 4 on yet). However, I'm in no position to insist that the client upgrades - either in side-by-side or in replace mode.

So that leaves them with whichever version of msxml.dll (and it's support files) come with their browser, now confirmed as IE5.5

And that, as far as I am aware, should be more than sufficient. But it just doesn't want to work...

 

[JustinEzequiel]

sorry strongm, didn't notice it was you.

i'll see if i can find a machine I can play with (have a couple of ideas...)

 

[JustinEzequiel]

this appears to work on a machine here at the office (Windows 95 with IE 5.0)

forgot to check MSXML version on said machine

did not work when I used MSXML2.DOMDocument
but did when I used Microsoft.XMLDOM

do not have time to check other machines as it is Saturday and my wife does not know I went to the office

[tt]Option Explicit

Private Sub Command1_Click()
Dim obj As Object
'Dim obj As MSXML2.DOMDocument

' Set obj = CreateObject("MSXML2.DOMDocument&quot
Set obj = CreateObject("Microsoft.XMLDOM&quot

obj.appendChild obj.createElement("root&quot
obj.documentElement.appendChild obj.createCDATASection("AS,FAS ASBFACSUKLDBFKQWGR578923HJB 4R23U4&quot

MsgBox obj.xml

Set obj = Nothing

End Sub[/tt]

 

[strongm]

Thanks once again.

I am indeed using MSXML rather than MSXML2, but you've got me thinking - I'm doing it via an added reference rather than via a late-binding CreateObject. Which may mean that my project (developed on a machine that has file version 8.0.6263 of MSXML) is trying to use the wrong CLSIDs, since the darn XML Install program always seems to hack them about.

So I'll try changing the code to late binding, as in your above example, and see where that gets me. I'll let you know how I get on.

 

[leyann]

Hello,
I think I've got the same problem with msxml.dll : When I add this file in my ActiveX package, the installation fails on 1 machine out of 2 (and the problem seems to be independant of Windows or IE version).
When I exclude it of my package, the installation works well but ask me for the Office Install CD on some machines... strange things...

 

[strongm]

Woohoo

Have a star Justin, you got me thinking along the right lines! Client has just confirmed that my latest, late-binding version works fine!

 

[JustinEzequiel]

glad to help, even indirectly