InfoPath Dev

From IP 2010, when you go to select your form type, you have the options of IP 2007 filler or browser. You can also change compatibility from the Form Options, or using Save As - I'm including a screenshot montage.

Hah - I knew something was off, but didn't put my finger on it - yeah, something was awry in that view. Some days I think IPFS is purely gremlin-powered.

Well, I guess it surprises me that it ever behaved any differently - I'd assume you'd need the OpenIn parameter to get the form to open in the browser from a link on a machine with InfoPath installed. However, perhaps one of the security settings in IE that is different between local intranet and internet was forcing it to open in the ...

Oh that is just weird, isn't it? The background thing? I get that message on forms that I've set to full trust and intentionally removed that alternate access path from - so I've seen it before - but really have no insight into what changed in your form that would cause it.

You may be able to simplify it a bit. For example, I think you could use relative paths instead of full paths for the XSN location (by the way, it looks like you have a typo there?), the Save location and the Source.

I do not know what you mean by: [quote user="jbungay"]publishes to a SharePoint list [/quote] Do you mean the form submits to a form library? Or is the form a SharePoint list form?

What does the link look like? Does it include the OpenIn parameter?

Your choices are extremely limited with IP 2003. With 2007, there is a function for adding days. I'm afraid the only option in IP 2003 may be code.

When it was being used as a browser form, the email submit wouldn't depend on what was installed on your machine. You can design InfoPath 2007 compatible forms using InfoPath 2010 - I try to keep everything the same version of Office on my machine (and keep a VM with Office 2007 for use with IP Visual Studio projects).