What happens to the form when DB is moved to production - InfoPath Dev
in

InfoPath Dev

What happens to the form when DB is moved to production

Last post 05-13-2009 03:38 PM by Hilary Stoupa. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 05-12-2009 07:17 AM

    What happens to the form when DB is moved to production

    Hi, I have developed an IP2003 form with a SQL DB at the background. Now, we are planning to move the database to a different server (a production environment). My question is, when the DB is moved, I will surely need to change the data connections to point to the new DB.. right? Won't that screw up all the validations on the fields? That would essentially mean that the form needs to be redone. Isn't it? Is there a way to avoid that? Thanks!
  • 05-12-2009 07:50 AM In reply to

    Re: What happens to the form when DB is moved to production

    Hi --

    As long as everything except the server will be the same (database name, table / view names, etc), you can save your form as source files and then, in manifest.xsf you can change the data connections to point to the new server.

    Make a backup copy first!

    Hilary Stoupa

  • 05-12-2009 08:46 AM In reply to

    Re: What happens to the form when DB is moved to production

    So, if the DB name changes then will I not be able to save the form? Also, once I save the sources, how can I rebuild the .xsn for publishing? Many thanks!
  • 05-13-2009 03:38 PM In reply to

    Re: What happens to the form when DB is moved to production

    Well, the DB name is used in the data tree.... so XPaths will change.

    To rebuild the .xsn, simply use File --> Save As and save as an .xsn. This repacks up your template files.

    Hilary Stoupa

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