InfoPath Dev

If you want to set all records to a value you can use a set field action.  If it is triggered from outside the repeating structure and does not ahave a filter for a specific row then by default all repeating fields will be set with the value.

This is difficult with a browser form since you cannot use a filter. I am not thinking of a way to do it since you cannot query the list like you could a web service to SQL or Active Directory.

That is the great thing about web services, you do not have to start over. The only way otherwise, with the default connectivity, is to start from scratch. You could use code to do it but that is difficult to setup and maintain. For web services you have to at least use SQL Express. Qdabra.com has a whole package of web services so that you can ...

Yes, this is a common issue with SharePoint, which I always have used submit to SQL to overcome, since a unique and sequential ID is created with each record insert.  I have seen many attempts at using Sharepoint by itself but I am not sure how many have been successful or whether having an occaisional duplicate is that big a ...

You can get an Active Directory Web Service or the whole set of tools in the download area. There are tutorials as well. Qdabra Database Accelerator Suite Version 2.1 - Developer

If you have the data connection created then you would just use a .Submit() to call the submit when you wanted from code.

It has been a while, but I thought you could use a formula and therefore concatenate any field you wanted in with some other text in the intro section.

So you want the forms to promote a field as a me column? You could setup a custom view, which only would show the user the forms which they modified. This is done in SharePoint and is out of the box functionality. Often there is some assignment field in the form that you want to use rather than who last submitted. So that the user assigned ...

I would link them via hyperlinks rather than attaching. Also I would look at whether the two forms could be combined into a super form with seperate views. You can ID the user and state when it is open to show the user the correct view and then it is much simpler to manage and relate the two.

You can use an Active Directory web service to identify the user and there login details. So if they have already authenticated you can piggy back on to it by linking their login to the form. You can also use digital signatures with their login. I would think once they have authenticated to get the form, which can also be dynamically secured ...