InfoPath Dev

Same reply from MSDN: You said 5 different pages on 4 different views, but InfoPath doesn't have pages - it only has views.  Please clarify. Submit = Save except that Saves make the user specify the filename, and they automatically save back to where they originated while Submits set the filename dynamically and submit to wherever the ...

Every form?  That's a ton of extra overheard for you.  It takes way longer to develop that way, requires farm admin access to update your template, and it causes an IISRESET every time you update the template.  That's a big no-no in a live environment.  I recommend only using admin-approved forms when they are ...

I am using InfoPath 2010 with SharePoint 2010. I have a large form that requires input from multiple authors and approvers before the form is finished. Let's say there are three groups of people that will be using this form, authors, managers and approvers. An author fills in a few sections of the form, then the manager reviews the ...

Hi Josera, Thanks, will try that out for my next form. Thanks!

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 ...

Clayton Why is it admin approved – I guess that is just an old habit.  All of the forms I created in 2007 where of this type, so I have just kept using it. Why use data connections – from what I had read I thought this was the best way to go. What I am really trying to do is to determine what is the best way to keep just ONE copy of a form ...

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.