InfoPath Dev

What you're trying to do doesn't sound very difficult and in fact can be done using rules in InfoPath as opposed to custom code.  You can create some formatting rules to disable controls based on values if you open the Rules task pane.  If you are curious about how exactly to do this in InfoPath, I can elaborate some more.

You can change the control to a Calculated Value and then you will have more control over the look and feel via formatting rules.  This will display the true XML value though, but in your case since its just a Yes/No field that can be easily fixed using some rules.

Looks like you have the checkbox and textbox bound to the same fields.  If you separate these into two different fields, then enabling the checkbox won't change the value in the other control.

I would first start debugging your form by extracting your condition statements and dumping them onto the form as calculated values to see what is going on.  Perhaps there is something wrong with your logic when dealing with existing documents that is causing the rule to fail.  Once you figure out why the rule isn't triggering the ...

You can try creating an database form in InfoPath designer.  Create a new form and you will see the option under Advanced Form Templates.

You can put all the controls you want signed in a section and make that section signable.  Do this by going into the properties of the section control and then turning on Digital Signatures. To block submit, you'll need to make your own submit button on the form and create a formatting rule that disables the button if that section ...

1) Yes you can populate the data on load instead of using a button.  You can either set data connection to auto load when the form opens or create a form load rule to query the data. 2) Yes you can create cascading dropdowns using term sets.

Also, so you know, this is a known IP "feature" - if you switch views and send email, the view won't have rendered and you get a blank email. You aren't doing anything wrong. Here's another post on this subject, about halfway down I have a simple sample form. We generally just have everything in sections in a single view and ...

I figured I'd ask this in the coding forum since this 2007 form does have code behind that grabs data from a SQL DB.  The form works flawlessly; however, when I publish updates to my SharePoint Library under Central Admin it takes about 4 minutes and then fails.  The whole time this is happening, I am looking at the server C: drive ...

Are you publishing to a SharePoint 2007 server?  If so, filters are not supported in 2007 on the browser.