InfoPath Dev

Bummer :( Did you try creating a "temp" field and setting the default value to the calculated value?  Then you can format the new temp field with the proper decimal settings.  If you don't want the extra field, you can try a calculated value and see if you get the format options there.

This sounds like a pretty basic workflow scenario.  There are a few out of box approval workflows that might be useful for you to at least start as a base and then expand on it as needed for your scenario. For more information, I've included links to a few articles that will hopefully get you ...

If you want to conditionally add or remove page breaks, I believe inserting them in a section and then creating show/hide rules on the section should work for adding/removing the page breaks.  With respect to detecting when a section will be larger than a printed page is going to be pretty difficult I think.  Unless you can ensure that ...

Try clicking on the control and opening up the properties.  Click on Format and setting the decimal dropdown there.

For your series of text fields, are they within the context of the repeating section?  That is, is the field under the repeating group node in your data source?  As long as the default value for this field, is using values within that repeating node it will only use the value for the current node.  My guess is that you just have to ...

I don't believe there is a way to remove the popup out of the box in InfoPath.  You can write custom code to send email which I think will avoid the popup from being sent.  Here is a blog post from Hilary that may help: http://www.infopathdev.com/blogs/hilary/archive/2008/08/24/so-you-want-to-send-an-email.aspx

Just searching online real quick, looks like the error has something to do with wsps.  Is that how you are deploying the solution to SharePoint?  Did you do anything else between when it last worked and when you saw this error message other than update the form?

I'm a little confused what the "wait for" actions are for exactly?  Why are they required in option one but not in option two?  If your form requires multiple approvals, there are a couple ways of doing it.  When the workflow kicks off you can assign multiple tickets to approvers and then what you get all the ...

Hi there, I don't believe there is a way of doing this out of the box.  Your options are the attachment control which encodes the base 64 within the form or a textbox/hyperlink control which doesn't give you the navigation you are looking for.  There might be a code solution or a custom control out there that might help, ...

If you already know the 3 people allows to view that particular field, there is the userName() function which will let you know who is the current user of the form.  Then all you need to do is to create a formatting rule that will check userName() against the allowed people.  If they don't equal, then hide the control.