Code

Re: thisXDocument.ImportDOM error

Greg Collins — Tue, 05 Sep 2006 17:21:05 GMT

Yes, "Import" is going to pull in additional data, not replace any.

If you want to replace the current DOM, try selecting the root node, and then doing a RootNode.parentNode.replaceChild()

Re: thisXDocument.ImportDOM error

philscience — Fri, 01 Sep 2006 20:57:10 GMT

Ok, I think I've got it. There were a couple of problems - newDoc was complaining about some things, so I turned off validation and loaded it a different way. This pretty much works now (although it is merging the new data into the form instead of replacing it, which I guess ImportDOM is supposed to do).

IXMLDOMDocument newDoc = hisXDocument.CreateDOM();
newDoc.validateOnParse = false;
newDoc.loadXML(transformedXml.ToString());
thisXDocument.ImportDOM(newDoc);

Re: thisXDocument.ImportDOM error

Greg Collins — Fri, 01 Sep 2006 18:00:15 GMT

The newDoc schema must match exactly that of your form or you will end up with schema errors that will prevent the form from opening.

Since you've said you applied an XSLT to the original DOM, that would indicate to me that you modified the DOM somehow--possibly changing node names, order or location. Any of these things will cause problems.

thisXDocument.ImportDOM error

philscience — Fri, 01 Sep 2006 16:28:51 GMT

Hi,

I am having some performance issues when using ReplaceChild to modify the DOM, and am trying to instead use this:

IXMLDOMDocument newDoc = thisXDocument.CreateDOM();
newDoc.load(transformedXml.ToString());
thisXDocument.ImportDOM(newDoc);

But when this runs, I get the following error:

System.Runtime.InteropServices.COMException
This form has an unknown structure.
#65279;#65279;
The XML Schema specified for this form could not be identified.

Has anyone run into this before? I have a feeling that it might be related to the newDoc, it contains xml that was created from running XSLT on the original DOM.