"VK" <schools_ring@y...> wrote in message 
news:1167838886.990564.306720@n......
> Martin Honnen wrote:
>> Make sure all documents involved belong to the same MSXML version (e.g.
>> in the above sample MSXML 3).
>
> To avoid this branch of possibilities: the MSIE's part of the
> initialisation block looks like:
> ...
>  INIT:
>  do {
>   try {
>    XSL = new ActiveXObject('Msxml2.DOMDocument.'+N+'.0');
>    XML = new ActiveXObject('Msxml2.DOMDocument.'+N+'.0');
>    DOC = new ActiveXObject('Msxml2.DOMDocument.'+N+'.0');
>    break INIT;
>   }
>   catch(e) {
>    --N;
>    continue INIT;
>   }
>  } while (N>2);
>
>  if (DOC == null) {
>   flagError(
>   'Automation server cannot create object\n' +
>   'ActiveX instantiation is blocked by security settings ' +
>   'or MSXML version is too old - 3.0 or higher is required.');
>  }
> ...
>
> This way either all objects initialized with the same ProgID or not
> init at all (goes to error handling).
>
> On the test machine the lowest supported version is used (3) and XML,
> XSL and DOC are successfully created.
>
> With XSL and XML loaded and parsed the next step currently looks like:
>    source.transformNodeToObject(XSL, DOC);
>    return DOC;
>
> With the code on page:
>  document.body.appendChild(transResults);
>
> gives error "No such interface supported" on IE6 which is tracked down
> to appendChild method.
>
> At the same time transResult.documentElement.tagName properly shows the
> root of the fragment (ol in my case).
>
Not sure what you're attempting? What happens if you display DOC.xml?
For a full example see the SDK:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsdk/html/ece045e3-85b3-46ed-85b4-8532f076ea79.asp?frame=true


-- 

Joe Fawcett (MVP - XML)

http://joe.fawcett.name