InfoPath Dev

 Don't worry about this. I redid all my rules to take account of weekends and public holidays.

 All, I've a form with a start date and an end date. I use this two dates to calculate the difference in number of work days, excluding weekends and public holidays. I then have a 'list of sections'. Each section contains a date, and two text fields. The first date in the list is the start date, then very simply ...

 Thanks, had to move away from a repeating table due to other reasons.

 I don't use the inbuilt validation rule. For me the compulsory fields are too easily missed. I've created my own rule on the final submit button, FormStatus must be X and Field X can't be blank etc. I also hide the final submit button within a section until all the validation checks have been passed. If the field is blank ...

 On your submit data connection, do you allow the file to be overwritten?

 All your buttons are technically submit buttons. Add a field to your form i.e. FormStatus. Your 'save' buttons submit the form to the library. Allow the form to over write itself if it is an existing form. Don't change the form status or change it to 1.Draft. You can then have your form open to whichever view  you ...

 Not for SharePoint on-line no.  

 Try creating the column in SharePoint first as a multiple person option, then publish the form, make sure the column/field names marry up.

You can set up a view and filter it by me. Make that the default view. Then you can use the all documents view as your review option. Read Only - several options. Create a read only view which opens up for end used based on  a criteria. Use a workflow to change permissions on the form itself. 

All, Using InfoPath 2010 I've a repeating table. I've changed the default value so that it automatically opens up with 5 rows. The first field in the repeating table is a date control. I can auto populate the table with sequential dates - ...