InfoPath Dev

I have a few conceptual ideas which I could make proof of concept for you if you don't have any luck. Sounds interesting and fun.

I've attached a form with two methods. The first is a bit stylish by having a checkbox (or radio button if you wanted) where the user can indicate the current row and a rule with an xpath filter on the output field retrieves the email field value from the selected row. This only needs code to mimic the behaviour of a radio button (to make ...

I've listed my 'repeat table header' findings here: http://www.infopathdev.com/forums/p/19481/67530.aspx#67530 and there might be something similar you can do to make the tables not page break in the middle of a row. A google for CSS styles for tables which supposedly address this behaviour gives: <TABLE ...

Look at me suddenly going all hoity toity with my 2007 Infopath - I should have remembered my roots! I'll upload a 2003 one for you tomorrow. But it's not an ideal solution anyway - if you are comfortable editing xsl files you might find this post useful: http://www.infopathdev.com/forums/p/19481/67530.aspx#67530

I can see how the xdPreserved bit (after Googling it) would work to stop Infopath auto-undoing, but I also read xdPreserves is not suitable for use in Browser based forms and the way they are displayed. Browser forms aren't usually in my scope anyway, but if I build a little 'tweak' tool to put <THEAD> tags into the xsl files ...

It's been asked many times how this can be accomplished. And there have been a number of clever methods attempted but I thought there *must* be a simpler way. Well I think I have it - Infopath stores the display formatting information for each of its views in XSL files, which are packaged up in the XSN template file. XSL files are XML ...

I've attached as close as I got. The method would require you to specify how many rows before a page break by changing the 'MOD' value in the conditional formatting expression. You could further fiddle this method to prevent the page break on the first row, but you would then not know how much of the page above the table is ...

You need to tell Infopath which row to update e.g. /my:myFields/my:group1/my:group2[2]/my:field3. would populate row 2

Check the 'Size' tab of the controls, and of the sections the controls are in. See if any of the 'margins' or 'border' values have been set to negative values. There might be some rendering dodginess passing those values to the text box and cause the text to draw 'offset' from where it should be. Another work ...

Well, normally I think controls are not wanted on a print view of a form. Without resorting to fairly complex means, and that's saying something seeing as what I'm about to suggest *is* a bit complex...or at least 'out of the box' Make little screenshots of the buttons and put them in place of the buttons on the print view. :-D