Re: problem with xml component(s)

Tech-Archive recommends: Fix windows errors by optimizing your registry

You haven't told us the underlying error details. After you get a False
return value from the Load() method, look in the DOM under the parseError
node and tell us what details are there

Tony Proctor

"vtxr1300" <cakewalkr7@xxxxxxxxxxx> wrote in message
news:1169157942.855474.187000@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a component that runs fine on a server, but from my local
machine will not run. All it does is open an xml file. The line below
that is commented out is the original that runs fine and the
uncommented line is one I tried by setting a reference to my own local
msxml component. I have granted full access permissions to everyone
for the file but it still gets into the err.raise -11 portion. In
another vb program, I'm calling this code and right before it I use the
filesystemobject and I can open the file and read it. So, I'm stumped
as to what might be wrong. Anyone have any ideas of something else I
could try? thanks.

'Set xmlDoc = CreateObject("Msxml2.DOMDocument.3.0")
Set xmlDoc = New MSXML2.DOMDocument30
xmlDoc.async = False
IsOk = xmlDoc.Load(FilePath)
If Not IsOk Then
Err.Raise -11, "GetString", "Problem Opening Source"
Set xmlDoc = Nothing
Exit Function
End If



.