InfoPath Dev

XML Spy is definitely useful. They have a free Home Edition, but it lacks the XPath testing capabilities of their $500 Professional version. There are other XPath testers available (try Download.com). You had a learning experience. It is likely you will pay much more attention to whether you are accessing an element or an attribute now. You may ...

It sounds like what you need is to use XDocument.GetDOM(''NameOfWebServiceDOM'').selectSingleNode(''//REPORTING_MGR_EMPLID''); or something to that effect. GetDOM() is used to get a reference to a non-main DOM. Does this help? Greg Collins [InfoPath MVP]

Without scripting you'll need to use the Open Rules. But this can be tedious if there are numerous fields. The best thing to do is to have the main data source (or at least a subsection of it) identical to the schema of the secondary data source. Then you can use script to just do a clone of the secondary data source, and then do a replaceChild ...

Yes, you are correct, you have to re-register a full trust form after each modification. Greg Collins [InfoPath MVP]

The place you want to look is in the thisXDocument.Errors collection. You can find out if there are any validation errors using .Count, and you can check the individual nodes that validation errors occur on as well. Greg Collins [InfoPath MVP]