InfoPath Dev

Are you using IP2007? If so, you could put all the rest of the form controls into a scrolling section and then the table above the scrolling section. While this isn't precisely what you were looking for, it may be a close enough mimic.

You are only getting the last one because each time through the loop, you are reinitializing the variable BodySeed1 to be equal to the value, and you are setting the appointment body to that variable. So, let's say first value is 'Elephant', second is 'Giraffe' and third is 'Panda'. First trip through the loop, ...

Note the syntax difference between your code and Jimmy's: you have a semi colon at the end of the foreach loop statement -- Jimmy has a curly brace, with a closing brace after the string BodySeed1 = BodyField1.Value;  line.

Hi -- Under Tools / Form Options if you look in the Advanced section (IP2007, 2003 may be a little different) you'll see an Edit Default Values button. Click that, and you'll be able to specify not including the node that the text box is bound to by default.

If your checkbox is associated with a secondary data source, it will display the current state of the records in the secondary data source each time it is queried. Since you most likely have set the query to run when the form opens, that means each time you open it, the form will display the most recent state of those secondary data source ...

Really, except for controls that the user is intended to use to fill out the form, the whole point of a template is that the user *won't* be able to edit it. You want to design your template so that the user would never need to open it in design view. In my sample, I've use expression boxes in the print view that have conditional ...

Do you have the controls in your view bound to the main data source now? I'm thinking from your description, that you initially had the controls bound to the secondary data source. If that is the case, the view will always show the secondary data source values instead of the main data source. If your 'if' condition is structured ...

A form view's print view is the way the form data will look when the form is printed. I wasn't implying any user activities, except, perhaps, that the user print the form, which I had thought was your desired behavior. If you have your form open in design view, and the task pane showing design tasks, select 'Views'. The bottom of ...

Hi, and welcome: Comparing your double eval formula to the one in the InfoPath Team Blog article, I'd expect to see: eval(eval(group2, 'concat(my:TotalResult, ";")'), "..") With group2 being selected using the Insert field or group function in the formual editor. You'll notice in the sample in the blog, the ...