InfoPath Dev

Currently what we have:

• Filler environment - XP and InfoPath 2007
• Design environment - mixture of XP and 7 with InfoPath 2010 saving into a 2007 format
• We are working on a template that may have multiple versions over it's lifetime with fields possibly being deleted and added
• They are published to a SharePoint library but it is used more as a file repository

Problem:

• When a user saves an old version of template and a new template is available they are not prompted to update, it is automatically done for them.  The old form should look and function as if it would on the version it was designed in. 

What I've tried:

• Tried various combos of File>Advanced Form Options>Versioning>
• set Update template to "Let form users decide when to update"
• set Update exisitng forms to: "Do nothing"
• The user won't get a prompt on their xml file, new design changes are applied, but new fields added aren't fillable(make sense here)
• I did notice in the xml file it references the link to the form on our SharePoint site instead of saving onto a cached file on their local machine.  I believe this is part of the issue but I have seen users in the past get the update message when a new form template is available but haven't seen it lately.

Help!

I'm not clear on what is the desired behavior  vs the current behavior.

If you want the old xmls to open with the old xsns, then use Do Nothing.

If you want the old xmls to get updated to the new xsn, then use Automatically Upgrade.

PS: Saving to the local machine is bound to cause issues. Ideally, all users are accessing the latest and greatest xml from the Sharepoint site, so as to not work with a potentially outdated xml that they saved locally in the past.

The odd thing is the templates are automatically updating on the local machine regardless of the option set to "Do Nothing."

The templates are stored on the sharepoint but their saved xmls are on their local machine.  Are we talking about the same thing?  We are in transition with our SharePoint 2007 to 2010 and don't want to invest more time into it.  That and we lack the knowledge and time to properly set it up.