InfoPath Dev

Hilary, thank you so very, very much for all of your efforts in trying to help me out. In the end I decided to fall back to an earlier, saved version and re-do all of my changes up to this version. It took roughly half a day, but I had already killed almost as much time trying to fix the other one. In the end, the lesson here is it's ...

Well, I did exactly that, and shown below is the edited manifest. Re-opened in InfoPath and saved and same result. I checked the text boxes too, and they are all blank. At this point I am wondering if I shouldn't go back to an earlier version of the form and re-do the changes...

The refresh didn't work. How/where do I access the raw data you show in your screenshot?

See attached

OK, it worked. I deleted an entire section, but that part has no relation to this particular bug. I've attached a truncated form. The specific text box I am having issues with is titled Project No. on the form. It's near(er) the top. The field itself is also called Project No. For me it displays the bug even in Preview, so you ...

Trying to think how I can do it. The form also contains a lot of XML that InfoPath does not save (another, unrelated bug). I've learned to work around that one by leaving my computer on 24/7 when doing development updates - I recode all the XML then never turn it off until I am satisfied with the update, then save and close - at which point ...

Hi Hilary, thanks for getting back. It's a list form. The text box no longer has any limitations or any rules applied. The field itself is at the default 255 characters. It displays the same 3-character limit in Preview, so it's clearly with the InfoPath form and not the list settings. Just for giggles though I created a test ...

So I was making some changes to my InfoPath forms involving validation to a specific pattern, and when I published it there was a 3-character restriction that wasn't part of any rule or validation I had set. The testers notified me of this and I verified it. I removed all rules and all restrictions, both for the text box as well as the ...

Thank you Hillary. Just before you responded I figured out I was doing something really stupid: had the drop-down set to "Matches pattern" instead of "Does not match pattern." It had been a while and I was a little 'rusty' coming back to InfoPath. Best regards and thanks again for responding!

So I am trying to do some basic authentication for the final year or so of our InfoPath tools, and am running into two very curious issues. The first field needs to always be a three-letter combination, to stand for city location (i.e. TWB). I have the authentication rule set to "must match pattern" and the pattern is this: ...