InfoPath Dev

Hello,

I am working with a informative tool that reports data and I want my end users to be able to remove the section control after they have done it but I do not want them to have to click the arrow then click remove I would prefer that on the click of the remove section arrow it takes away without the extra click necessary.  I would prefer that by doing this it does not change the show function on the section control so if they need to reference what they just did they can easily show.  Any instructions anyone has for me on this would be greatly appreciated. 

 Thanks

Hi, Drew:

 I'm sorry, I'm afraid I don't quite understand what you want to do. You want to remove an optional section after it has been filled out? Removing it would also remove the data. How about just hiding it? You could add a helper field to your data source with a boolean data type, and give the user a button to click for showing or hiding the section. Clicking the button could set the boolean to true or false. Your optional section could have conditional formatting to hide the section if the field is true, show it if the field is false, or something along those lines. Does that make sense? Or did I misunderstand entirely?

Hi Hilary,

 Let me try to give you the scenario a little better then before.

So i have sections with read only data that i want to have the end user have the ability to hide when/if not needed.  Since the information in these are more like placeholder text its not going to erase anything since no data in these fields will be end user text. 

The way infopath does this right now is have you click on it and then click again to hide.  I want it to on click (without menu) hide the optional section.

Hope this helps :)

And thanks for your help :)

I would make it a regular section, not optional, and use conditional formatting to show/hide it. You could even use a set of option buttons to show/hide and base the conditional formatting off that.

As far as a way to modify this functionality using code, you may want to look at this on MSDN on the View.ExecuteAction method.