InfoPath Dev

Update: - Setting the 1st repeating field in a repeating table to a tab number does NOT work.  - Setting a tab order # on the repeating table (thought with might force focus to first field), but that does NOT work either.  The tab order # on a repeating table is ignored. Resolution: Put an ALT # on 1st ...

@alberta If that's the case, then my suggestion in my earlier post (modifying the schema file) would probably be enough.  Before you do that, though, I would recommend doing the check I mentioned at the end of that post to make sure that the data connection is bringing in the rich text in the first place.   @starkey I apologize ...

Hi Anson, Yes, I tried that approach too but thank you.

 Hi Jimmy,  Looking at your qRules list, it looks like the CopyRichText command won't work with web Browser forms (http://www.qdabra.com/en/products/qRules_requirement.aspx). Thanks

Kind of, the Description rich text data "copied over" from the secondary data source is for display only, no need to be persisted in the Proposal form. Thanks

Thanks for the quick response.  1.  so you think that if I make hidden fields 5-10 part of the tab order, then the tabbing will skip to 11 because the html does not know that 5-10 exist? 2.  awesome that I can skip numbers. 3.  will let you know about the tabbing to repeating table using a tab number in the first field ...

I'm trying to find a way to use a sequential numbering system to name forms that are submitted to a forms library in SP 2010 (also Infopath 2010) The form naming convention will be OPxx where xx is a sequential number. 1 number higher than the previously submitted form. I created a field LastUsedNumber and when the form loads there are 2 ...

Thanks, that sounds a bit icky, I might just put the rule on the drop down 9as it is now) and add it to the last text box.

I'm thinking when you change the field and tab out the form probably sends data to the server (including the current value of the field bound to the checkbox).

When you have differences in behavior between the client and server, the first culprit is likely the postback settings.  If that's not the solution, then it's likely a bug! :)