InfoPath Dev

Hi Stacie, If your SQL table already has constraints, stored procedures are a good way to go. Hilary has blogged this recently here: http://www.infopathdev.com/blogs/hilary/archive/2009/10/13/use-dbxl-submit-with-existing-sql-data.aspx If your SQL table does not have any constraints, however, the best practice here is to not write any ...

How about changing the schema to add one parent section that contains the two sections and putting a signature on that parent?

Bind the dropdown to a secondary data source and then set the values using your script. Should be samples everywhere on this site (probably Greg has some in his blog), but that's the general technique. People with InfoPath 2007 can use qRules to do it without code.

You don't need code for 1. 3. 4 and 5. Check out Clayton Cobb's SharePoint Madness blog for a technique. It isn't a best practice though since two people can submit at the same time. To prevent duplicates, you should submit the form twice. Submit it once without closing. Query to get the SharePoint list ID. Set it in your form and then ...

Add a button to your form. Change the button to Rules. Add one rule with an action that submits to SharePoint and another rule with an action that submits to your database connection. Piece of cake!

Hi Scott, You should consider using two form templates of matching schemas. One form is used to generate the "default values" for the other one. So that when they double click a form saved from XSN #1 it opens up a form of XSN #2 with prefilled questions. In other words, the questions are data-driven. I can show you an example of the ...

Should be fine. You'll want your labels to be expression boxes pointing at a secondary data source that can be switched to flip between English and Chinese.

Why not filter it out in the repeating table first. In other words, don't let them enter duplicates in the first place. Should be able to check when they enter and if it exists already show a warning and/or set the field to blank. You could also look at qRules which will help you do filtering and other commonly requested commands that require ...

Hi Davie, So you have forms saved to SharePoint and those forms are also submitting to SQL? Is that correct? If the SQL DB has changed, you can use Tools->Convert Main Data Source, but you are right that this will invalidate the old forms because the InfoPath-SQL is a tight coupling. We advocate using Web Services and data-driven ...

I think content types may be your answer.