-
Ah, my error -- perhaps we only get that option for a main connection that a form is based off of.
However, you can bind a regular section to a repeating group -- I only get the first row of my data back, but it does work....you can right click the group in the data source task pane, select More, and select Section with controls for example.
-
Not on the submit button -- I think you want to do this in Open rules. Under Tools / Form Options / Open and Save there is a place for rules that run on open.
-
So if I edit the properties of the submit button, I can select "submit using custom rules" and create 11 different rules, based on each view and say, "If the department is equal to __dept name___ switch view to __dept name___"?
I'm not sure what you mean by a "hidden field" - how do you enable ...
-
That did the trick!
Many Thanks!
-
Hi Hilary,
Thank you soo much Hilary, I was just looking for the solution if it is possible through code or not. I think the same, has you said it is not possible through the code. Okay I will follow the method which you have suggested me early. Had a great discussion, I'm very much thankful to you. Good day...
Thanking ...
-
It's sql - talking to a view in the database. Hitting 'modify table' on the connection I get three drop downs for sorting the data. There's nothing I can see there for 'multiple rows'. Am I looking in the wrong place?
-
What is your secondary data source? If it is SQL, in the wizard where you create the connection, there is a 'modify table' button that when you open it has a checkbox for 'multiple rows' (my labels may be off, don't have it open right now). If you deselect that, you won't have a repeating structure.
-
Why do you have to do it in code? I don't understand that requirement at all. I don't believe InfoPath gives us any programatic access to the controls on the form itself, only the fields bound to the form, so a coded solution may not be possible in this case.
-
I can't help but notice that in the code sample you've posted, you have exactly the same namespace as was defined in my sample. Since Infopath bases the namespace off the date and time the form was created, it seems unlikely we created our forms at exactly the same date and time.
One way to find the namespace for your form is to save it ...
-
Well yeah...obviously, if you use "Cannot be blank," then it cannot EVER be blank. That setting is not conditionally-based. You need to turn that off and instead add data validation to that field that says "If RadioButton = AttachOption and AttachmentField is Empty (or blank maybe), display error." This will ...