InfoPath Dev

Crazyness. I'll try to keep it simple. I'm trying to understand what might be the cause. Two forms, one called JOBS and one called VALUEADD. JOBS has a main data connection to a SQL Server table called ''NEWJOB''. VALUEADD has a secondary data connection to NEWJOB from which I query data from NEWJOB through custom code. The problem: When ...

We narrowed down the problem. The problem is in the taskpane.js that is part of the download. The following code returns 'nothing' when you have a datafield that is linked to a database field. Can anyone tell me how this needs to be modified so database related fields will actually return a value? var sXPath = ''''; var oPathNode = ...

Still don't have it. BILLINGINFO is a table in a sql database. engCommentCode is a field in the table. When you look at the xml of the INFOPATH FORM, engCommentCode is not a ''Tagged'' field like other infopath fields are, but rather an extenstion of the table name. <q:BILLINGINFO billingID='''' jobID='''' jobNo='''' billAmount='''' ...

Thanks for the reply. However I'm missing something. The xpath to the data field is Field xpath=''/dfs:myFields/dfs:dataFields/d:NEWJOB/d:BILLINGINFO/@engCommentCode''> When I plug that into the help.xml that came with the download, nothing displays in the task pane. If I use a field that I created in the form itself (i.e. myFields/zipcode) ...

The datasource is from the main source, however, it is only a ''retrieve'' and not a submit.

We are having trouble guessing what the right xpath is for the custom taskpane help form. We have a non db field which we get to work fine with the example downloaded. The Xpath is rather simple ''<Field xpath=''myFields/zipcode''>Enter Go brown.</Field> When we try to display help on a repeating database field, nothing ever shows ...

We made a change to a form. Now when I open up existing forms, we get the following message. Element 'http://schemas.microsoft.com/office/infopath/2003/ado/dataFields}COMMENTHISTORY' is unexpected according to content model of parent element 'http://schemas.microsoft.com/office/infopath/2003/ado/dataFields}NEWJOB'. Expecting: ...

We have a repeating table that is linked to a database table. When you add records to the table and submit the form, the corresponding table gets updated. We added fields to the database table. We modified the data connection so we could include the new fields We changed the binding on the repeating table to include the new columns Under Form ...

We have several hundred forms that exist. We want to add another field/control. Everything adds ok, however when you open any one of the existing forms, the newly added control is greyed out. How can we activate this new field on existing forms?

Matt, Thanks for the direction. I did more digging and found other threads that discuss filtering the secondary datasource and we got it to work. I'll probably come back to the Stored Procedure at some point, but right now, we are going to just use the Filters. Thanks!