InfoPath Dev

I believe I've found the problem which may be useful for others to know. On further investigation, the latter list boxes were limited by the number of rows in the first list box.  The reason for this is, the InfoPath data connection wizard defaulted the relationships between the tables to the primary key field for each.  Thus if ...

OK good to know. Thanks Greg

Hi Greg, I know Microsoft usually seek feedback for improvements to their product and as an MVP, maybe it would have more pull coming from you (if you agree with the suggestion). What would be useful in a new InfoPath version would be to add a selection to the 'Action' drop down within the Rules wizard to include something like 'Run ...

I have applied the cascading list box approach with a database connection in a form I have built.  I have created a simple Access database to test. When I make a selection in the first list box, the second list box provides filtered data accordingly.  However, it only seems to show the first 15 values of the filtered data.  Is ...

Hi Clay, Again thanks for your suggestions. I have tried a couple of them without success and the others are beyond my skills. Fortunately we are able to get some consultant time, so hopefully they can suggest a suitable approach.

Hi Clay, Thanks for the answer. My main reason for using the SharePoint fields is because I need the workflow to change the values so the form can use these values for it's logic (views, data validation, conditional formatting).  My understanding is that promoted fields from the form are read-only in SharePoint and can't be ...

Further investigation reveals that if I select the 'Include data for the active form only' check box in the data connection wizard, I don't get the inheritance problem.                            The new problem is, I can't seem to get access to ...

I've published a form to a forms library.  The forms library has a number of fields I created (SP_WorkflowID, SP_SaveAsDraft) whose default value is set to 0 from the Form Library settings.  The form itself has the same named fields (WorkflowID, SaveAsDraft) which are populated from the forms library field values as part of ...

After being able to add a row, I realised I would need to be able to remove a row. Here is some code to remove the last row, you could modify it to remove a selected row. Dim parent As XPathNavigator = MainDataSource.CreateNavigator.SelectSingleNode(''/my:myFields/my:group3'', NamespaceManager) Dim lastchild As XPathNavigator = ...

I sat down with a colleague and we nutted it out. For those who may need help for the solution in VB, here it is: Dim newxmlstring As String Dim newrow As XmlDocument = New XmlDocument Dim Parent As XPathNavigator 'Build XML needed for empty node newxmlstring = ...