<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>General</title><link>https://www.infopathdev.com:443/forums/41.aspx</link><description>If you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: Problem designing renamed XSN file</title><link>https://www.infopathdev.com:443/forums/thread/30238.aspx</link><pubDate>Wed, 09 Jul 2008 14:05:27 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:30238</guid><dc:creator>Clay Fox</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/30238.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=30238</wfw:commentRss><description>&lt;p&gt;Hey Jeffrey.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;nbsp;think the publishing part is what you have been missing.&lt;/p&gt;
&lt;p&gt;If you use Explorer view on the document library you will find a hidden folder called forms, inside that is the template.xsn.&lt;/p&gt;
&lt;p&gt;You can copy that to your local hard drive and rename it to work on it.&amp;nbsp; You also should be able to open it, switch to design mode and then save as, if you have not disabled this.&lt;/p&gt;</description></item><item><title>Re: Problem designing renamed XSN file</title><link>https://www.infopathdev.com:443/forums/thread/30235.aspx</link><pubDate>Wed, 09 Jul 2008 12:10:42 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:30235</guid><dc:creator>gl44guy</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/30235.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=30235</wfw:commentRss><description>&lt;p&gt;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?&amp;nbsp; I dread having to recreate it from scratch.&amp;nbsp; And does working locally include a network share?&amp;nbsp; I and another person share design responsibilities.&lt;/p&gt;
&lt;p&gt;I had tried saving locally and renaming, and then uploading to sharepoint, but the template pointer issue remained.&amp;nbsp; Perhaps because I uploaded instead of published?&lt;/p&gt;
&lt;p&gt;Also, when I first started using Infopath not long ago, I tried creating the form locally.&amp;nbsp; When I put it on sharepoint, other users could not open the form because it was looking for my local path.&amp;nbsp; Again, perhaps because uploaded/saved it to sharepoint rather than publish?&lt;/p&gt;
&lt;p&gt;I appreciate your responses.&amp;nbsp; I have a time crunch (isn&amp;#39;t it always?) and I hate the idea of doing it wrong and wasting everyone&amp;#39;s time.&lt;/p&gt;
&lt;p&gt;Jeffrey&lt;/p&gt;</description></item><item><title>Re: Problem designing renamed XSN file</title><link>https://www.infopathdev.com:443/forums/thread/30231.aspx</link><pubDate>Wed, 09 Jul 2008 05:56:52 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:30231</guid><dc:creator>Clay Fox</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/30231.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=30231</wfw:commentRss><description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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&amp;nbsp;from the&amp;nbsp;Sharepoint location you may have some issues.&lt;/p&gt;</description></item><item><title>Problem designing renamed XSN file</title><link>https://www.infopathdev.com:443/forums/thread/30208.aspx</link><pubDate>Tue, 08 Jul 2008 17:23:12 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:30208</guid><dc:creator>gl44guy</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/30208.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=30208</wfw:commentRss><description>&lt;p&gt;I created an InfoPath&amp;nbsp;form in Shared Documents called &amp;quot;Purchase Request&amp;quot;.&amp;nbsp; I have since needed to rename it.&amp;nbsp; I can open the newly named file to complete the form, but I cannot go into design more.&amp;nbsp; I get an error saying &amp;quot;Could not open &amp;quot;....../Purchase Request.xsn&amp;quot;.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;The next box says that &amp;quot;InfoPath cannot open the following file: .../Purchase Request.xsn.&amp;nbsp; The file cannot be accessed.&amp;quot;&lt;/p&gt;
&lt;p&gt;That is the old file form name.&amp;nbsp; I cannot figure out where this reference is.&amp;nbsp; Perhaps a template?&lt;/p&gt;
&lt;p&gt;I am not site admin, but not a site collector?&lt;/p&gt;
&lt;p&gt;This is very frustrating.&lt;/p&gt;
&lt;p&gt;Lastly, what is the best practice for working with forms, as far as where to edit it?&amp;nbsp; I have been keeping in on the sharepoint site since at one point a &amp;#39;local&amp;#39; form appeared to hardcode my local path with Windows login ID.&amp;nbsp; This caused problems from other workstations.&amp;nbsp; So I just put it on the server.&lt;/p&gt;
&lt;p&gt;I appreciate any help.&amp;nbsp; While I wrote a pretty good form (I think), the renaming and best practices are my vice at the moment.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item></channel></rss>