InfoPath Dev

InfoPath 2007 provides date calculations. If you are in InfoPath 2003 or 2007, you can use managed code which has wonderful date functions, like AddMonths(). If you are using script, you will need to do all the footwork yourself to make this function as it should. You should be able to find appropriate help in a JScript or VBScript forum.

Your correct XPath entirely depends upon exactly what current() evaluates to. For example, if current() evaluates to my:group2, then current()/my:ddlTeamName makes sense. However, if current() evaluates to my:group2/my:SomeOtherField, then you would need to use a relative XPath to get back to the one you want, like this: ...

Yes, that is the best approach. It makes life much easier!!

Please note that I have only looked over your code, and have not actually tried to run any of it.  ERROR 1: You don't need to create a new app. Just reference XDocuments directly. ERROR 2: You are missing your quotes.Microsoft.Office.Interop.InfoPath.Application myApp = new Microsoft.Office.Interop.InfoPath.Application();  // ...

Thanks for sharing this. I know it will be very useful to people in similar situations! I'm glad you got it working.

Great! Hopefully they will add it. I know I could definitely use that feature!

Try removing the link between them (i.e. turn off the master table back into a regular table from the properties dialog) and disconnect the details section the same way. Now go back and set the table to a master (i.e. give it a name), and then link the detail section to that master table. If for some reason this does not do it, you might need to ...

The main location to add the default value is template.xml. Other than that, also updating the sampledata.xml to match the change you made to template.xml is a good idea. These should be the only required changes. You should not need to modify myschema.xsd.

This is not possible due to sandboxing. However, you can modify the view .xsl file and add the style='cursor: xyz' to the <input type='button'/> tag.

To answer your first question, no there's no limit to the number of options that can be shown in the drop-down list box control. However, an excessive number of options will have performance issues. Try removing the filter to discover whether it is a problem with receiving data from the db connection or whether it is a fault of the filter ...