-
SHAPE is very powerful and is your best choice in a situation like this. It will let you create a hierarchical structure that you can use to display your data in the format you desire.
For example you might return a structure such as:
<Make name="Toyota" idcode="1">
<Model name="Corolla" ...
-
You cannot design the XML in the MAIN DOM at runtime. However, you might be able to pull this off in a secondary DOM. Even though there is a schema associated with the secondary dom, InfoPath doesn't hold you to it at runtime. So you might be able to pull that off.
HOWEVER!! In order to design the view to display those dynamic tables, you ...
-
That is difficult as InfoPath only allows you to specify a single print view. Without doing your header/footer in the view (and not as an actual header/footer) I don't know how you will be able to do this. . . but then this complicates things, now doesn't it? And I guess that having the user print, switch views and print again is obviously ...
-
What is your reasoning for not using the builtin header/footer feature? If you are using InfoPath 2007, they've made it possible to include field values in them.
-
1. Does your model table have any field that specifies the manufacturer so that you can filter?
2. Can you, instead of doing 2 SQL queries, just do a single query that returns all the correct data already in the format it needs to be (using the SHAPE command)?
-
You will need to add the repeating XML structure to your DOM using code. How to do this will depend on the code language you are using ... there should be several examples within these forums... look for "insertBefore" or "appendChild".
-
I just made a quick test form and it worked just fine without adding the space... make sure that you max function is returning a valid number.
-
First verify that max(@TRASPORT_NUM) is returning a valid number. If not, see what's wrong there.
If it is returning a valid number, then try adding a space between the max() and the +1: max(@TRANSPORT_NUM) + 1 ---sometimes that can actually make a difference, as weird as that sounds.
-
-
The red dashed border is an indicator that the field value does not match the data type. For example, placing alpha text into an interger or date field.