-
It's certainly possible, but I need to understand your situation a little better.Does the child table have a column that has the IDs of the corresponding parent table row?Does your InfoPath form have the owner ID already?If the answer to questions 1 and 2 is "yes", then you only need to query the child table in the first ...
-
QueryDB does not allow querying more than one table or view at a time. If you would like QueryDB to retrieve data that combines the data from two or more tables, what you can do is set up a view on your database server that exposes the data you want, and then use QueryDB to query that, using the syntax described in the documents you ...
-
You should be using something like [../@ID = current()] here, not the full path inside the brackets, but I don't think that's what's causing this error. Are you sure that the capitalization of ID is correct and that you're using the correct namespace prefixes the whole way? Could you attach a screenshot of your ...
-
It would help if you could tell us the actual error message and not something vague like this:
[quote user="spegg"]I tried to add it to mse and debug but got an error saying something about DOM and debug manager.[/quote]
The problem might be that you're using the wrong capitalization for DOM in these two ...
-
Please make sure that the SelectionNamespaces declaration towards the top of the .js file includes the dfs namespace (prefix and URI), and add it if it's not there.
-
You need quotation marks around the value of any XML attribute, so either:database='#Resumes#'ordatabase="#Resumes#"
-
Does your main data source have a my:List node directly under the my:myFields node, whose namespace is different from the myFields namespace? You need to put your data into nodes that are defined in the structure of your main data source.
-
You can use a layout table to arrange two sections side-by side.
To reduce a section to its minimal size, put your cursor inside the section and press delete and backspace a few times to make sure there aren't any extra line breaks in it. Also open up the section properties and make sure that the height is set to ...
-
Looks like you're missing an end-parenthesis.
-
You can create a rule as the first rule in one of the fields' set of rules that has a condition, and the option "Stop processing rules when this rule finishes." That should stop the infinite looping, but it's up to you to determine what the stop condition should be.