SQL Database Integration

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

Hilary Stoupa — Wed, 13 May 2009 22:38:53 GMT

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.

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

shivajidatta — Tue, 12 May 2009 15:46:29 GMT

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!

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

Hilary Stoupa — Tue, 12 May 2009 14:50:07 GMT

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!

What happens to the form when DB is moved to production

shivajidatta — Tue, 12 May 2009 14:17:43 GMT

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!