-
You may be able to do this with rules, but you'll need a lot of them. You'd need to set rules on each of the fields that are bound to the date pickers, with conditions -- for example, if only one date picker field has a value, that should be the one in the text box. If more than one is filled out, your condition will need to compare ...
-
I'm afraid I'm still a little confused. You are saving to TWO different SQL servers? Or just one? If your form is not built off a database, you won't be able to submit to a data base unless you use a web service. Your current form that you use in the first step, is it based off a database? Does it submit directly to SQL?
-
Hi --
You wouldn't need code, I'd think. Just add a button and add an action to query using the same data source as the repeating table connected to the list.
If you must use code, the code would vary according to the language you are using or whether you are using InfoPath 2003 or 2007.
-
Hi--
If you switch the view and send the email in the same ruleset, you'll get a blank email, I'm afraid. From this InfoPath team blog entry that has a work around: "In the InfoPath rich client, you'll still only see the blank view due to view-switching concurrency limitations."
-
Yup, and the terminology... you know how it is, you have to know what its called to be able to Google it. Glad that fixed it!
-
I'd create a view in the SQL db that combines the two tables and use that as my data source for the drop down list. As you've noticed, you can only select one data source for a drop down's value / display pairs in IP, so a view or code will be the only way to do this....
-
It might be an interesting exercise to add a text box or expression box to the form that is bound to the same field as the date picker -- make sure they don't have any date formats applied to them, that they just show the XML value.... see if you are getting the 'yyyy-mm-dd' format that IP expects...
-
Have you been to Office Online? This link is to the publishing section... perhaps it will be of some assistance.
-
Is your form already saved as source files? If not, rename the .xsn with a .cab extension. Then, open the .cab file and copy out all the form files. This will give you access to manifest.xsf.
-
I think perhaps there is a background set on the view in the form. Open the form in design mode and, while in the view of the form that has this background, select Format / Background Color and set the color to white. This can also be done from the properties of a view.