Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / General MS InfoPath Questions / May 2005

Tip: Looking for answers? Try searching our database.

How do submit repeating group but not rest of the form?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Daryl Scarlett - 19 May 2005 11:09 GMT
Hi i have created a form which contains details about an incident based on
incident number.  There is a repeating section which contains details about
the people involved in the incident and there can be more than 1 person
involved in each incident.  Is there anyway that once details about one
person have been entered that the information can be sent to the database
just for that person and then the data cleared allowing for another person to
be entered with the same incident number.

Hope someone can help?
Greg Collins [InfoPath MVP] - 20 May 2005 20:27 GMT
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.

Signature

Greg Collins [InfoPath MVP]
Please visit: http://www.InfoPathDev.com

Hi i have created a form which contains details about an incident based on
incident number.  There is a repeating section which contains details about
the people involved in the incident and there can be more than 1 person
involved in each incident.  Is there anyway that once details about one
person have been entered that the information can be sent to the database
just for that person and then the data cleared allowing for another person to
be entered with the same incident number.

Hope someone can help?
Daryl Scarlett - 23 May 2005 09:56 GMT
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?
Greg Collins [InfoPath MVP] - 25 May 2005 23:12 GMT
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.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.