" Bob" <bobatkpmg@yahoo.com> wrote in message
news:%23CibVmnbEHA.2660@tk2msftngp13.phx.gbl...
> I'm wondering if one node that belongs to one XmlDocument can be appended
to
> another XmlDocument as a new child without having to build a new node from
> scratch. I would think XmlNode.Clone() is for this purpose but no, it
> doesn't work. I got the following error:
>
> The node to be inserted is from a different document context
>
> Does anyone know if this is doable without building a new node and without
> putting through XSL?
>
>

Bob wrote:
> I'm wondering if one node that belongs to one XmlDocument can be appended to
> another XmlDocument as a new child without having to build a new node from
> scratch. I would think XmlNode.Clone() is for this purpose but no, it
> doesn't work. I got the following error:
>
> The node to be inserted is from a different document context

"bruce barker" <nospam_brubar@safeco.com> wrote in message
news:%23tIqcCobEHA.1764@TK2MSFTNGP10.phx.gbl...
> you have to build a new node and create your own copy function. if
> performance is not the top issue, use the InnerXml/OuterXml properties to
> copy.
>
> -- bruce (sqlwork.com)
>
>
>
> " Bob" <bobatkpmg@yahoo.com> wrote in message
> news:%23CibVmnbEHA.2660@tk2msftngp13.phx.gbl...
> > I'm wondering if one node that belongs to one XmlDocument can be
appended
> to
> > another XmlDocument as a new child without having to build a new node
from
> > scratch. I would think XmlNode.Clone() is for this purpose but no, it
> > doesn't work. I got the following error:
> >
> > The node to be inserted is from a different document context
> >
> > Does anyone know if this is doable without building a new node and
without
> > putting through XSL?
> >
> >
>
>