-
You don't bind the drop-down itself to the repeating element, you right-click your drop-down and choose Properties, and then set it up to be populated from that repeating list.
-
Secondary data sources, by their nature, contain their default values within them. For example, if you have a 2DS connected to an XML file, that XML file contains all the default values... these are not set at runtime unless you use rules or code.
-
You shouldn't need code for this. Add a secondary data source which links to your Access database. You can set up a button which forces a query to take place. Then bind a repeating table to the repeating node in your secondary data source (from your Data Source task pane).
-
Also, as you see on Agni's example, the [1] should be on the node and not the attribute.
-
By the nature of the beast, any time you import or update a schema, InfoPath will lock it because it cannot guarantee where it came from. Only schemas built directly in InfoPath (yeah, yeah, you could argue that it was -- but that was from a different form) are editable.
Now-- one thing you can do, is extract the form files from both forms (the ...
-
Make sure your XPath is correct and that you are using the appropriate namespaces (if required). You need to know where your starting point is for your XPath...
For example your could need to write:
sum(../my:RepeatingNode/@my:Total_Cost)
or
sum(SomeNode/@Total_Cost)
etc.
-
If there is a failure in the code in your OnLoad event handler, the code just jumps out of the event without reporting a failure (this is only true for the OnLoad event). To alleviate this, try placing your code in a try/catch block to see if a failure is happening somewhere.
-
The main DOM might be read-only in specific situations (like during OnBeforeChange or OnValidate events), but in general it is not read-only as Agni says.
-
Hi edove,
Thanks - not a problem... I hope you are able to get the answers you need here!
-
Great! Glad you were able to figure it out!
Keep up the good work!