Problem designing renamed XSN file - InfoPath Dev
in

InfoPath Dev

Problem designing renamed XSN file

Last post 07-09-2008 07:05 AM by Clay Fox. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 07-08-2008 10:23 AM

    Problem designing renamed XSN file

    I created an InfoPath form in Shared Documents called "Purchase Request".  I have since needed to rename it.  I can open the newly named file to complete the form, but I cannot go into design more.  I get an error saying "Could not open "....../Purchase Request.xsn". 

    The next box says that "InfoPath cannot open the following file: .../Purchase Request.xsn.  The file cannot be accessed."

    That is the old file form name.  I cannot figure out where this reference is.  Perhaps a template?

    I am not site admin, but not a site collector?

    This is very frustrating.

    Lastly, what is the best practice for working with forms, as far as where to edit it?  I have been keeping in on the sharepoint site since at one point a 'local' form appeared to hardcode my local path with Windows login ID.  This caused problems from other workstations.  So I just put it on the server.

    I appreciate any help.  While I wrote a pretty good form (I think), the renaming and best practices are my vice at the moment.

     

     

    Jeffrey
  • 07-08-2008 10:56 PM In reply to

    Re: Problem designing renamed XSN file

    Best Practice is to keep a local copy of the XSN for design purposes and then Publish the form to the appropriate document library to update.

    This should take care of the issues and is what InfoPath looks to do by default. If you are accessing and editing the file directly from the Sharepoint location you may have some issues.

  • 07-09-2008 05:10 AM In reply to

    Re: Problem designing renamed XSN file

    Is there any way to take the form I already have working and move it to a local location so that it is no longer linked to the sharepoint site?  I dread having to recreate it from scratch.  And does working locally include a network share?  I and another person share design responsibilities.

    I had tried saving locally and renaming, and then uploading to sharepoint, but the template pointer issue remained.  Perhaps because I uploaded instead of published?

    Also, when I first started using Infopath not long ago, I tried creating the form locally.  When I put it on sharepoint, other users could not open the form because it was looking for my local path.  Again, perhaps because uploaded/saved it to sharepoint rather than publish?

    I appreciate your responses.  I have a time crunch (isn't it always?) and I hate the idea of doing it wrong and wasting everyone's time.

    Jeffrey

    Jeffrey
  • 07-09-2008 07:05 AM In reply to

    Re: Problem designing renamed XSN file

    Hey Jeffrey.

     

    I think the publishing part is what you have been missing.

    If you use Explorer view on the document library you will find a hidden folder called forms, inside that is the template.xsn.

    You can copy that to your local hard drive and rename it to work on it.  You also should be able to open it, switch to design mode and then save as, if you have not disabled this.

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