-
You are using absolute paths in your code. That is why you are always getting the first instance of the nodes. Your OnAfterChange event is already pointing to the correct field1... you just need to get the sibling field2 and field3... not go all the way back to the top of the tree...
There may be other issues too, but try the following ...
-
Please be more specific about which viewer you installed. XML files will be displayed in whatever application is specified for that file extension if InfoPath is not installed.
Greg Collins [InfoPath MVP]
InfoPath Dev
-
Once the form is saved to the library, it is an XML file. You simply need to load the xml file from its saved location and then do whatever xml things you need to do with it.
Greg Collins [InfoPath MVP]
InfoPath Dev
-
You will need to build the body content yourself in code. That may not sound very pleasant if you have a lot of fields, but that is what you will need to do.
Greg Collins [InfoPath MVP]
InfoPath Dev
-
Try
IXMLDOMNodeList elemList = thisXDocument.DOM.selectNodes(''//my:field1'');
foreach(IXMLDOMNode elem in elemList)
{
string s = elem.text
// do something with elem content.
}
Greg Collins [InfoPath MVP]
InfoPath Dev
-
Check your schema. It might not be set up the way InfoPath likes it. Best to have the RT field as a child to the repeating node.
Greg Collins [InfoPath MVP]
InfoPath Dev
-
You might be able to do an XMLHTTP put out there... otherwise you'll need to do a Full Trust form and write the saving code.
Greg Collins [InfoPath MVP]
InfoPath Dev
-
You should be able to attach the debugger to the application once its launched. This doesn't do much for OnLoad, but it should get you in if you need to debug other areas.
Greg Collins [InfoPath MVP]
InfoPath Dev
-
This usually happens because your expresion box is bound to the same node as another editable control on the page. This is typically true for Rich Text controls.
So maybe you have a Rich Text Box on the page somewhere and also an expression box, and they both point to the same schema node.
In this case, there's nothing you can do about it. I've ...
-
I believe that current() usually represents the node to which the control is bound.
Greg Collins [InfoPath MVP]
InfoPath Dev