-
What do you mean by the statement that "since the users will be able to save different versions of the form"? That's not the case unless you give them the template (XSN). If you have SharePoint, you just publish it to a SharePoint form library (new or existing). If you don't, you can publish to a network ...
-
Explain how you configured/built the form and how it's getting sent. It sounds like you are sending the template instead of an XML file based on the template.
The form should be published to a set of email recipients using the publishing wizard.
-
Sure, it's quite normal to show blank controls - they are almost always blank on form load anyway. How exactly are these controls configured to show that data, and why can't you set default values? Are you referring to controls bound to nodes on a secondary data connection?
-
Isn't all of your code for the form written using the 07 object model? The error does reference the OM of the code not being supported. I don't know what all code you have, but you'll need to go to Tools > Programming and ensure the Form template code language is set to C# (InfoPath 2003 Compatible) or Visual Basic ...
-
Yes, you can't just save it with 2003 compatibility and expect it to work. Saving it as 2003 means it can only have things that were available if you built it in IP2003, which removes all the benefits of using 2007.
All of your users should be on the same version of Office. If not, that is an organizational problem that must be ...
-
It worked right away. I did check the box for allowing editing on each of the 4 fields. Screenshot attached that shows the version history. I changed the state to GA from AL on the 3rd submit, but even the first submit showed it was going to work...
-
Well, we'll have to do some digging, but I can tell you that all of my promoted fields that are allowed for editing in SharePoint do show up in the version history when changed. I'm looking at one of my form libraries now, and one of the things I change with workflows is the workflow status (a value within the form). I have to ...
-
Yes, I think you are. What do you mean when you say you published the InfoPath form but it is checked out to you? When you publish your template, it does not go into the library itself. It goes into the hidden Forms folder (for back-end use only) and replaces the built-in template.xsn file that is there by default when you create ...
-
Oh wow, now I think I understand. So you aren't using _any_ of InfoPath's abilities other than a simple way to fill out a form, right? You are just opening the template (XSN) locally, filling it out, then saving it as a data file locally (XML). You are then right-clicking on the file and choosing Send To > Mail ...
-
That's getting a bit picky now. =P I'm not sure how to do that without code. I worked through some other ideas, but I can't figure it out. Is there a reason why you prefer a dropdown list that must be looked at multiple times instead of a multi-select control?