https://www.infopathdev.com:443/forums/41.aspxIf 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.enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/52712.aspxMon, 15 Mar 2010 15:59:46 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:52712admot0https://www.infopathdev.com:443/forums/thread/52712.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=52712<p>Here&#39;s the scenario. I currently publish an xsn as &quot;C:\Forms\Shipping Order.xsn&quot;.&nbsp; I place this file into two non-Sharepoint locations for two sets of users. The form is stored in location A as &quot;Shipping Form.xsn&quot;. The problem is Location B stores the files and places in underscores in the name i.e., &quot;Shipping_Form.xsn&quot;. There is no way to turn this off on location B. Unfortunately, the name cannot be changed anymore.<br /></p><p>Location B users will have problems receiving updates since their file names are Shipping_Form.xsn and the form was published as Shipping Form.xsn.</p><p>Besides republishing the form prior to posting to location B or telling users &quot;Please open xsn after each update to refresh cache&quot;, is there another programmatic solution that is a bit more automated?</p><p>One idea is to programatically update the xsn prior placing on location B. http://www.infopathdev.com/forums/p/3988/15745.aspx </p><p>&nbsp;</p><p>Any other options?</p><p>Thanks! <br /></p>