InfoPath Dev

Yes it is InfoPath 2007. My solution might be to have a third view on my form.  Have a print button that passes the needed values to that view (and to my other view for database posting) and then print the data in that view.  That way each time the button is clicked on the repeating section that data is transferred to the correct ...

I have a form with a repeating section so I have the main data in the top part and the ticket information in the repeating section.  I need to be able to print just the data in a specific repeating section combined with the main data.  So the user will click print and print just the data in repeating section one.  Then later click ...

I am not sure I know what search terms to use to find the blogs on the subject.  Is there a limit on the number of rules?  I am assuming that the more rules you have the slower the form?  I need to accomplish the same thing and thought that I could get RepeatingSection[@NodeCount]/my:Field1 where @NodeCount is the count of the node ...

count(parent::*/preceding-sibling::*) + 1

OK I have a form with two views.  View 1 (Office View) links to an Access database.  View 2 (Pit View) contains text boxes.  I am using Pit View to create a print version with the SDK.  Office View pulls data from Pit View to be posted back to the database for reports and billing. My problem is in my repeating sections.  ...

 I ended up making a second view with unbound fields and made those fields the values for the database linked fields.

I have an InfoPath form that links with an Access Database.  I have installed the InfoPath SDK to create a ticket in Microsoft Word so I can print a 9.5 by 5.5 document.  Unfortunately none of my fields show up to be placed on the Word document.  The XML Schema shows the database fields if you open it up in Notepad.  When I ...