This sounds like what i would want. Can you talk me through it in more
detail please so i can give it ago? Infopath newbie
> I guess that would depend on you database design. If you allow for non-unique incident numbers... then that should be fine.
>
[quoted text clipped - 9 lines]
>
> Hope someone can help?
You will need another field in your repeating section that will identify whether that item has been submitted. Just before you submit, you mark that field as true. If the submit fails, mark it back as false (because it really didn't submit).
Filter your repeating list to only show items that have not been submitted (that would be the new one you create each time).
As I said before, every time you submit, you will keep submitting everything (included previously submitted ones) because they are all still there in the form -- you just can't see them. This shouldn't be a problem if you don't expect to have a large number of items before the final submit is done.

Signature
Greg Collins [InfoPath MVP]
Please visit: http://www.InfoPathDev.com
This sounds like what i would want. Can you talk me through it in more
detail please so i can give it ago? Infopath newbie
"Greg Collins [InfoPath MVP]" wrote:
> I guess that would depend on you database design. If you allow for non-unique incident numbers... then that should be fine.
>
> Otherwise you might look into posting to the database, then "hiding" the filled out row by marking it as posted, and having a new row ready to fill in. Ultimately with this you'd be sending the same data over the line mulitple times though.