InfoPath Dev

Hi - no, I can see of no reason that you can't open in design mode. Except perhaps that in IP 2003, there was a button you could click to "design this form" and now there is not? I think if you open InfoPath Designer (2010) and under File / Open put in the URL of the template you wish to design, you'd be able to open in design ...

There should not be any issues with this. If your IP 2007 form has code, it cannot be sandboxed in ShP 2010, but would require admin approval (just as in ShP 2007). That is the only thing I can think of that would be different than using IP 2010 with ShP 2010.

Oh, that's too bad, I was hoping that would work. You'll just have to use substring functions in that calculated value to parse the date out the way you want it, I'm afraid. You can find a sample form here.

Is the control a text control? If you change it to a calculated value, in the calculated value properties, under "Result" on the General tab, you can choose how to format - you may want to try that, and change it to "Date", and try a different format.

NaN = Not a number. Do both Current Principle and Appraised Value have values? Did you add the same condition as to Appraised Value being > 0? You can modify your rule to set the field to just the value of Appraised Value, and then just the value of Current Principle, so you can see what those values are when your form opens, that may help ...

Is the Appraised Value field in a secondary data source? When those initially load, they aren't considered "changed", so rules set on them don't fire. I'd add a rule to form load (if the data source loads when the form opens) to set the Current Appraised Value, or whereever else may be appropriate for your form's logic ...

Hi - all you need to do is add another submit connection to your form that submits to your SharePoint library. Under your submit options, change the form to use rules. One rule submits the form to SQL, another to SharePoint. No code needed. By the way, in general, you'll see more functionality available in filler forms vs. browser, rather ...

If the referreral field is not getting set in the form, of course, there is no data in the field to submit, then. Perhaps deactivate most of your rules and just try your submit and query rule to see if you are getting data back in your query? Drag the query datafields onto the form to verify you have the data you'd expect?

Does the command fail with the same error as your initial post? If you change the lookup column to text (temporarily) does a value get submitted there? The only thing that looks off to me is the mapping for your referral field: /my:myFields/my:General/my:referral I would use XPath relative to the repeating group: ../../my:referral Your rules ...

Well, you could add some data validation for this, I suppose - check that the years and months match (using substring functions to get the separate pieces of the date) - but it won't prevent the user from being able to pick a different date - just prevents him / her from submitting. You could also reset the field to blank if the date selected ...