InfoPath Dev

Hello, I am trying to use button in infopath to submit values from repeating table into webservice to send to sql.  I've used this example...  http://www.infopathdev.com/forums/p/10879/38732.aspx  I am learning visual studio at the same time.  I am getting the underline in this example --> ...

I am wanting to submit to webservice on click of button, i followed an example, using VS 2008, infopath 2007...  Public Sub CTRL370_5_Clicked(ByVal sender As Object, ByVal e As ClickedEventArgs) Dim mainDataNavigator As XPathNavigator = MainDataSource.CreateNavigator()Dim SubmitSubName As XPathNavigator = ...

I know infopath can be submitted to sharepoint and save as with concat(field1, field2) but my problem is, when creating a new project site, you have to configure that submit button to send to that specific library.  All of these forms are in the sharepoint template and would hate to have to redo a submit button and republish every ...

I am using 2007, I know there is an option to use the unique values but it still lists all of those repeating values or i am just not telling it where to filter properly after that box is checked to display a unique value.  I will look into the SQL side to see if there is anyway to prevent the duplicates.  There are 28 items per ...

Preceding sibling is probably the best way to go to get rid of the duplicates in a single dropdown.  The dropdown is using a datasource from SQL.  I have it filtered on a ID number which works fine but there are too many duplicates.  I've tried running all kinds of filters but i still can't reduce the list.  Tried ...

 Yes i finally got it what I needed to do, I realized that it was in the wrong text box and now its works smoothly when you said this "the rule that is bound to a field will only fire if that field changes."  Thank you for your time!

I have a little section of calculations, very simple nothing to complicated but somehow it isn't working. (I also have hidden fields to help set these correctly SetQuant and SetFootage) Its also set up to keep the boxes filled with 0 in case it is blank so the calulations will work with rules.  Txtbox A will always calculate ...

ok, sorry for your waste of time, this was major user error on my part.  Sometimes working on a form for so long can get your locked up and can't think anymore.  Its been resolved.  Thank you.

The 2 buttons have the same type of rules with different ID numbers. It's there for convience and for looks.  It has same rules. LKup 1 sets a value to Txtbx A and Lkup2 sets a value to txtbxB.  The select box is in a repeating table, using current() to help set to the txtbox correctly.  works fine.  The lookup1 has a rule ...

Thank you for your response.  The ID numbers are different.