InfoPath Dev

The simplest answer would be to turn on versioning for the form library. But if you want them all available in the library at the same time, you could just modify the file name on each submit to create a new XML file - then you have to worry about people opening / updating the correct one, of course, so that may be icky.

You could add another column to your SharePoint list with the date in the format you'd prefer, and use that column for the Display for your drop down, the other for the Value. Or you could use substring functions in your default value to put the date back together - here's a sample form that has some different Date formulas that might ...

Hi - the alternate access path is part of the publishing process - at least if you publish to a network location, you have the option of publishing to one location, then providing an alternate path in case users can't access from the original published location. I'm not sure where you are publishing this - I'm not sure what a form used ...

I think the issue may be that the behavior you are describing is unusual. Perhaps no one else has run into it?

I've attached a sample for you to take a look at. Right click the link in the heading of this post. Save the file locally. Right click and select "Design" to open in design mode from your saved location. Then you can preview, take a look at the logic, etc. Let me know if you have questions.

Use an expression box (IP 2007) or calculated value (IP 2010). You can use a formula that adds up your fields.

.. moves you to the parent - here's a W3 Schools page with a bit more explanation.

What about allowing them to save the XML locally and then re-open and submit once they are connected? Or is "send automatically" a requirement?

Did the new form overwrite the old template? Or does it have a new name? If the name is different, the old XML will be linked to the previous template, and will need to be relinked (you can to this in the form library - there is a relink view for this).