Problems in publishing Infopath form - InfoPath Dev
in

InfoPath Dev

Problems in publishing Infopath form

Last post 01-10-2008 06:40 AM by Clay Fox. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 01-10-2008 02:43 AM

    Problems in publishing Infopath form

    Hi,

    I want to publish my InfoPath form and use it.

    But I cannot give the xsn file to the user as they can work with that and make changes.

     

    I tried Installation option and network service option. Both these options allows the user to save the xsn in their locale and edit.

     

    I also tried publishing to SharePoint  which gives the user only the preview and not xsn. But there user needs to go to the document library and click the new button.

    Is there any way to open the new document in the document library , from a simple ASP.Net page on a button click event. The form is not browser enabled. There fore I’m not getting any URL when I click the new document link there.

     

    Any help is appreciated.

    Thanks

    joseph

     

  • 01-10-2008 06:40 AM In reply to

    Re: Problems in publishing Infopath form

    Hi Joseph.

    The user must open the XSN file to begin a new form. That is how InfoPath works.  You can give them read only to the XSN so they cannot change it.  You also can turn off design mode in the form so they cannot edit it as redily either.  When published to a network share or SharePoint you can give them a URL link to the form directly.  You can also set up the form so that it submit or saves to a different location then the template but they still need read access to the template to open an existing form since it provides the information of how to present the data.

    In SharePoint, the exact location of the template is at http://<server>/<site>/Forms/template.xsn So if the document library is at <server>/<site>/Test then the template is at <server>/<site>/Test/Forms/template.xsn

    Hope that helps.

Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.