Hi InfoPathers:
I have 2 views in my InfoPath 2010 filler form, one called Configuration and one called Test Plan. The idea is that a developer fills in the configuration information for a team setup, that causes certain tests to appear on the test plan page, and a tester goes off and runs those tests.
In order to keep the tester from having to flip back and forth between the two views, I've put some repeating tables on the Test Plan view that are bound to the controls entered by the developer on the Configuration view, usually in a repeating table. The idea here is to give the tester the ability to view the configuration information, but not make changes to it.
The vast majority of the controls on the Configuration view are comboboxes, and when I create the corresponding controls on the Test Plan page, I make those textboxes, which I can then set to read-only. However, I have one set of three checkboxes I need to bring over from the Configuration view, and I'm struggling with how to make these read-only. I can set up a formatting rule that evaluates to true every time and then disable the checkbox, but then the checkbox is also disabled on the Configuration view. Not good!
Does anyone know is there's a way I can get the name of the current view without having to resort to custom coding? I do see there are some custom coding options using the CurrentView property, I'd just prefer not to have to deal with custom code if at all possible. Alternately, what about an option that would let me use a different control that I can set to read-only? I did come up with an option that let me use textboxes in lieu of option buttons in a different section of the Test Plan view, and that let me use the read-only property of the textbox. Because I need the possibility of multiple selections, checkboxes or a multi-select list box seem like the best options, but I don't see a way to make either of those read-only aside from using the current view.
Any help greatly appreciated!
nkstrou
An imprecisely defined requirement has an infinite number of possible solutions. Unfortunately, only about a maxiumum of 3 solutions are actually satisfactory to the end user.