InfoPath Dev

Hi exemplaris, Instead of writing code and using optional sections, you could just use a normal section with conditional formatting to hide the section when your drop-down listbox is not the odd choice. Would this work for you?

Hello , as i was using the search no good answer came up. so please pardon if I double post. my problem: (Infopath 2007 -webform -  and sharepoint 2007) I Use a sharepoint list as an secondary datasource. The user must use a checkbox option for his selection The form was already created I added some workflow (SP) so that we can use ...

Ted, thank you for the quick reply. I guess I am really a beginner at this and not sure how to go about doing this. My example...to better explain myself.....   Cost Center General Name CCRMD-KOSTL CCRMD-KTEXT CA06002202 Mat Logx LAC CA06002203 Ret & Rep LAC CA06002210 Pr Shop Indir LAC CA06002211 Buf ...

I am a newbie to InfoPath 2007, so I need a little help. I have designed a pretty basic form for a plant inspection, it has check boxes (ok and not ok) and text boxes (issues found).  However it is 17 pages long, with approximately 100 text boxes for issues found...so I would like a view that will show the text box only if the "not ...

Hi CrystalA, I created the secondary data source in MS Access and exported it as XML although you can create the XML resource file any number of ways (notepad for example).  You can also use a SharePoint list as a secondary data source too. Not sure what you mean by your second question though. Ted

Unfortunately, InfoPath is "sandboxed" meaning that you cannot do a lot of the cool interactive things you can do on a web page. I don't know any control (other than a drowndown or list box) that would give this kind of functionality. Text boxes allow for auto-complete, but this is different: based on what was typed previously. You ...

It does require you to write code to insert a node/group when a selection is made (and then delete it again when the seletion changes). You might also look into the Qdabra.com qRules product which has an Insert command that can do this too. This doesn't require code.

Option buttons are grouped together on a single data node. Depending on the value of the data node, one of the option buttons (or none of them) will be selected. Each option button allows you to choose the value which identifies it as being set. So by default the values are, "1", "2", "3", you can set them manually to ...

 You can either set it at design time in the data source task pane, or you can set it at run time using rules (such as an open rule).

Yes, that is a strange oddity that I've run into. The solution I've found for this is to not leave the other edges with no border, but to set them with a border set to the background color--typically white, but whatever it is. This makes those little hangover lines disappear.