InfoPath Dev

We use IP 2003 and as a result, we email a lot of .xsn files around for processing.

 We discovered an issue and not sure how to plan for it.

We store the final xsn files in a library (some in SP, some in network drives and some in a file storage system).

The original templates are all in a forms library in SP 2003.

If the template every gets moved in the forms library or deleted as no longer used, the older forms can no longer be opened.

Since we know we will eventually move to SP 2007 and IP 2007, our SP structure will change.

 How can we ensure that our current forms are able to be opened and viewed over time?

Thanks

Hi OldRadio99,

Do your forms contain custom business logic (i.e. code)? Extract the source files from the XSNs and look for a file with a dll or js/vb extension. If one exists, you have code. If you have code you may have hardcoded dependencies in the code. That needs to be checked.

If you don't have code, you're likely facing migration issues for the data connections. If it's the default SharePoint data connection, you should try republishing manually. If that fixes it, it's a simple issue. If it doesn't, it's probably because you have other data connections that need to be fixed up, i.e. migrated. 

There are two tools for migrating XSN solutions from one server to another. We sell a command line tool for SharePoint 2003 at:

http://www.qdabra.com/proddetail.asp?prod=QDeployment

Microsoft also makes available a tool as part of SharePoint 2007:

http://www.microsoft.com/downloads/details.aspx?familyid=B8683A1C-CF4B-4D81-9234-38542F8D5039&displaylang=en

Good luck!