 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWordDirectoryUser Groups Related Topics Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ... |
MS Office Forum / General MS InfoPath Questions / August 2005Publishing/Updating
I know how to publish a form for my users to access, but what happens when I need to update/make changes to this form (ex. changing data connections, text, etc...) Do I make my changes to the original form, then 'republish' overwriting the published file? Hi, Assuming you have a backup copy...yes! <G> Keep in mind, when you have published an XSN each "XML" file created from that XSN is "tied" to that XSN in that location. One of the benefits of InfoPath is that when you make a change to the XSN, existing forms will automatically pickup those changes the next time they are opened! (This assumes you have not changed the default behavior.) I hope this helps! Best Regards, Scott L. Heim Microsoft Developer Support This posting is provided "AS IS" with no warranties, and confers no rights So for example, I have my access database and xsn files stored in a folder called "Groups" on a shared network. I publish all the xsn files to another folder called "Public" on a shared network. My question (which you have probably answered, but want to better understand..) is when I need to update/make changes and/or change data connections, do I do this on the original xsn files in the Group folder OR the published files in the Public folder? Also, do I leave the database in the Groups folder? Or do I need to copy it into the Public folder (I'm assuming the answer is NO, otherwise I'll lose the data connections and will have to rebind?)? Thank you for all your help! > Hi, > [quoted text clipped - 14 lines] > > This posting is provided "AS IS" with no warranties, and confers no rights. Hi, The question is: what XSN is going to be used by your users? In other words, what XSN will they "double-click" to start a new form? The answer to that question will answer which XSN needs to be updated. Now, you can either update that copy directly or update your "original" copy and re-publish - either way is fine...just be sure to have valid backups before you make design changes. The database can stay wherever you desire...as long as the users that are opening the form have access to that directory. Do you need to move the database? That's up to you - if it's "not broken" then don't "fix it!" :-) I hope this helps! Scott L. Heim Microsoft Developer Support This posting is provided "AS IS" with no warranties, and confers no rights Okay that makes sense. So which ever XSN I tell the user to start a new form (let's say: Published XSN).. this is the file to make changes/updates. I would ask then.. what is the point of having the 'published' function.. but I'm guessing its to have the original XSN as the backup?? Hi, The benefit is you would have a "local" copy to work on while your users continue to use the currently published version. When you are ready, simply republish the form to the appropriate location - this way there is no interruption for users. Scott L. Heim Microsoft Developer Support This posting is provided "AS IS" with no warranties, and confers no rights Thank you! You've been GREAT!!! My pleasure! Take care, Scott L. Heim Microsoft Developer Support This posting is provided "AS IS" with no warranties, and confers no rights |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.