msxml4

[tweety]

I had a problem with IE 6.0.2800. The responseText property of the
XMLHTTP object was giving an error.There was a bug in msxml dll. so i
upgraded to
msxml4 and changed the code to the following:


try
{
var xmlhttp = new ActiveXObject("Msxml2.XMLHTTP.4.0");
}catch(e)
{
try
{
var xmlhttp = new ActiveXObject("Msxml2.XMLHTTP");
}
catch (E)
{
alert ("Please upgrade your Internet Explorer.Aborting ... " );
}
}

If msxml 4 is installed in the system then the code works fine.If there
is no msxml4 then it doesnt work. It gives an error
"Could not set value property".

If the code is like this:
try
{
var xmlhttp = new ActiveXObject("Msxml2.XMLHTTP");
}catch(e)
{
try
{
var xmlhttp = new ActiveXObject("Msxml2.XMLHTTP.4.0");
}
catch (E)
{
alert ("Please upgrade your Internet Explorer.Aborting ... " );
}
}

then it works in a system without msxml 4 but gives the same error
"Could not set value property" in a system with msxml 4.

Why doesnt it take the statement inside the catch and create the
object?


This problem is only with Windows 98.

 

[Martin Honnen]

I had a problem with IE 6.0.2800. The responseText property of the
XMLHTTP object was giving an error.There was a bug in msxml dll. so i
upgraded to
msxml4 and changed the code to the following:


try
{
var xmlhttp = new ActiveXObject("Msxml2.XMLHTTP.4.0");
}catch(e)
{
try
{
var xmlhttp = new ActiveXObject("Msxml2.XMLHTTP");
}
catch (E)
{
alert ("Please upgrade your Internet Explorer.Aborting ... " );
}
}

If msxml 4 is installed in the system then the code works fine.If there
is no msxml4 then it doesnt work. It gives an error
"Could not set value property".

On which line exactly, if a line number is given in the error message?
Is that the exact error message you get an an English version of
Windows? Or some translation?
It does not look like an error message being caused by those statements
above.
Is IE 6 installed when you get an error? Note that for IE 5 for instance
with a normal install there could be neither Msxml2.XMLHTTP nor
Msxml2.XMLHTTP.4.0. Of course the try/catch would catch that and that
error message can't be explained by that either.

Lots of questions, but make sure that you try to establish that the
error comes from those statements above or post some context.