-
To publish multiple InfoPath forms into a single SharePoint library requires SharePoint 2007. This is a new feature of SharePoint which allows you to have multiple types of forms/documents in a single library. I think you need to use content types to accomplish this, but my memory here is a little rusty.
-
When you say you updated from the browser what do you mean? Did you make edits in the form then click save or submit?
-
Hello Cindy and welcome. Sorry no one ever responded to this. I would need more information about if your data query is on the Main Datasource or a secondary data connection. The values should automatically update after teh query completes.
-
Hello Stuart and welcome to our forum. This is an interesting one and we haven't tried this yet. When it asks you to bind to the datasource it is asking you to bind to the Main XML datasource. I am not sure that you can bind it to a secondary datasource (Your access db).
-
Welcome to our Forum Franck. Glad you found the answer. Looking forward to your participation in our forum and to helping you with your InfoPath projects.
-
Hi Rob and welcome. To use the HowTo the easiest method is to right-click the manifest.xsf, click ''Design'' then from inside the designer click Preview. Also from designer you can click save or publish to properly setup the xsn to be opened directly.
-
When you look in the design checker, also click the link at the top to show the compatibility dialog. There is a setting there to enable the form to work on the Form Server. Ensure that is set correctly.
-
I do not believe this is possible. You can set the print orientation per view in the View Properties dialog. If you really wanted the user to be able to choose orientation a work around would be to create two views with exactly the same form (copy/paste) but one set to portrait and the other to landscape. Then you could have the user switch to ...
-
Your project will definitely require code either in InfoPath or Word to achieve. You may want to consider a Word SmartDoc solution instead so your users don't have to deal with two applications in this scenario.
-
Instead of sending the XSN file you should send an InfoPath XML file generated by the server and the server can inject the sequence number before sending. Since the XML file already will have a reference to the proper XSN deployed on yoru intranet it will just open correctly.
If you must send the XSN in the email as your deployment method, you ...