InfoPath Dev

Hi guys,

The Problem:
After the initial form version is in ciculation for a while the form owners change their forms. They remove fields and add new ones to keep the forms aligned with their changing requirements. However, for auditing purposes we need to keep the old submission accessible. Since InfoPath seperates template and submission we are getting in trouble if an old submission still points to the location where it finds a changed template (fields are either not displayed or an error message prevents the form from opening if the data source doesn't match anymore).

The only solution I see so far is to create a new template with a distinctive reference whenever the form is changed. Since our DMS doesn't cater for this automatically this would involve quite a bit of discipline of our users and is therefore not really reliable.

Anybody had similar problems? Does someone have an idea for a smarter solution?

Thanks a lot,
Tobias

Hi Tobias and welcome!
Yes, you can change the name of the published solution every time you change it (and publish to a new location). You can also use a product like our Database Accelerator that supports audit tracking and reporting on multiple versions. Send me e-mail if you want more info. Good luck!

I'm having a similar problem. Changing the template can make the forms already filled in unopenable. Is there a way to way to get around this(for completed forms and partially complete forms)besides recreating everything elsewhere as this is not very viable for me.

Hey,

If you are publishing to Sharepoint, you can use this method to have multiple versions of the same form published to the same form library.

http://www.infopathdev.com/forums/topic.asp?TOPIC_ID=2923

MB