InfoPath Dev

Thats not hard then. Add a new field called Submittable (Name as you like) should be a boolean, set to false. In the Submit button, setup a new rule that checks to see if either box1 OR box2 is checked, Add Action set Submittable to true.  In the Submit button, setup a new rule that checks to see if each box1 AND box2 are ...

I am a little confused on how you want the validation. Are you trying to to make sure both check boxes are checked before sending the email? Or, just want to notify the user that one of the boxes has not been checked and it can be emailed as is?

Using the View properties Read-Only works great, but not for file Attachments, as you have noticed.  One of the oddities of IP I suppose. The only thing I can think of would be to manually change each property to read-only.  It can be cumbersome. To get the attachments working on the read-only view where each individual field has been ...

Are you asking how to make an attachment field not changable when the form is read only? Or how to make the actual attachment read-only? It's easier to control the attachment field than it is to control the actual attachment.

The way you save the infomation depends on how it is used. EX: We track documents from begining to end, with internal archiving happening within the form itself.  This has to be self contained within one form, or you would end up with a SP list thanks extremely long and not really easy to read. In your case, it sound like your using the SP ...

No you don't have to. That just makes things more complicated.  In order to update a SP list, you will have to a CAML update.  It requires more overall work, but can accomplish the same thing. I assumed you were using forms, but it makes no difference which you use.

When you save the forms, are you using a data connection or the submit button geneterated by submit options. (if using the submit options, go into data connections to find out the data connections name, may or may not have "submit" in its name) Go into the data connection and make sure the Allow overwrite if form exist is checked. ...

How do you have InfoPath naming the files that are saved into sharepoint? Are you choosing the names and designating a field to be the filename or letting InfoPath auto-create a name?

You could do all this in one form.  3 different views: New Item/Check for existing Item VIEW Insert Item VIEW Update Item VIEW When the user opens a NEW form, its would give them the New Item/Check for existing Item VIEW This would be where they could insert there first info, maybe a number, a name , etc. When they ...

Updating the way you are thinking Patrick would work if they are using a database, but if they are using sharepoint forms(xml), it won't work since InfoPath has to save the xml back into sharepoint. So I guess the question to the OP is: Are you using a database or a just sharepoint xml forms?