InfoPath Dev

You can only print in InfoPath using the Print Preview button in the toolbar, but nothing in the toolbar can be affected at run-time, so it's either always there or never there.  If you need it to sometimes NOT be there, then it has to ALWAYS not be there.  Then, you no longer have the built-in print capability and would have to add ...

As Patrick mentioned, toolbar buttons cannot be affected at run-time.  They are either on or off.  I, too, recommend disabling Save/SaveAs/Submit/Views/Close (leave only Print Preview unless it's not relevant) and instead use custom Submit and Close buttons in the form, because they can be conditionally formatted.

No, I've never seen that happen.  I just created a form with a Date Picker and Text Field, made both required, previewed (saw the red asterisks), then published and opened in the browser (saw the red asterisks).  Both worked as expected. What are the details of your validation?

The cause is too many actions occurring at one time (i.e. parsing through data connections, setting field values, filtering data, etc.), which slows down the form and invokes this error.  You have to either use a different browser or make the form more efficient.  It's really annoying and only happens in IE.

Answered on MSDN: http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010customization/thread/b96f99d7-86e8-481f-addd-a70ad4ed192d It all boils down to the fact that you can't have browser forms without SharePoint unless you go with Qdabra's Forms Board.  That is the only alternative that I know of. Please close that thread.

I highly recommend not putting spaces and special characters in your filename like that.  It can be done with substring manipulation, but it is highly recommended not to do it the way you're asking.

Do you really need it to be in another report? Is this using SharePoint or just InfoPath standalone?  If using SharePOint, you just create views with summed columns so that you can see the totals for all relevant values by slicing and dicing the metadata.  If it's standalone, then I don't know how you'll consume all that data ...

How exactly did you publish it?  What were the exact publishing steps and options chosen while publishing? You're actually getting that error AFTER it publishes?  I am not aware of a Finish button.  The last button before publishing is "Publish," and then after publishing, it has a "Close" button.  The ...

Do they actually disappear, or are they not there on your default view?  You need to make sure they are visible when the form is submitted to email.  I would think you would be doing one of 2 things: Switching to a view that contains the buttons without conditional formatting and switching to this view before the email submit action ...

Create a new column that concatenates the two values and use that column as your DisplayName value of the dropdown.  I'm not sure you can consume calculated columns into InfoPath through list data connections, so you may need to create a simple SPD workflow that sets the value of this new field (make sure it's hidden from the user by ...