InfoPath Dev

This is a database bound form, right? Created from a database? And the scanId field is set up as an auto-incrementing identiy column? I haven't worked much with DB bound forms lately, but I if I recall correctly, this scenario should just work -- InfoPath knows the Id will come from SQL when the form is submitted, and doesn't worry about ...

Is your form set up for browser compatibility? User Roles are not compatible with Browser forms, unfortunately. Here's an Office Online article on adding User Roles to your form, too.

Any chance you are changing the view right before sending?

I usually start by changing my section binding from a group in the data source to just a random field. Here is a blog post that discusses this with repeating sections, hopefully it will help with your section.

Here is a lab at MSDN that may help you get started.

If you know what your form will be named, you should be able to figure out the link to the form -- generally it is http://servername/libraryname/formname.xml. Are you using IP 2007? I know in IP 2007 when you create your email submit, you can choose to include the form in th ebody of the email. I can't remember for IP 2003, I'm afraid. ...

A lot will depend on the structure of your form, and what you are trying to summarize. In general, however, you can use expressions boxes with filtered XPaths to display specific information from your repeating tables. You could also add additional repeating tables to your form that are bound to the same repeating group as the ones where your ...

There are a couple possible issues with this. Since the scanId column is auto-incrementing, I anticipate either SQL or InfoPath will complain if you try to set the value yourself The scanId is created when the data is submitted. If you set it when you open the form, you could have issues with mutiple rows having the same scanId. For ...

For item 2, does this happen if you close and re-open the document after submitting? DBXL writes the Doc Id into the processing instructions of the XML, so on the first submit, that information won't be there, and if the XML is not closed and re-opened, DBXL won't know that the document already exists. For item 1, I'll have someone ...