InfoPath Dev

Does not contain is not the same thing as equals.

One last thing as I know you've been very helpful (as always) and need to move on. What Xpath formula can I write using the "does not contain" action? As always thank you very much

Contains or does not contain are used for things like checking a string for a substring. So - you could see if an instance of a field contained "abc" or "def" or "ABC" or "DEF".

Thank you very much for the clarification Hilary. Moving on from that (and I know this should be another post but I only ask here because I know you already have a copy of the form that I sent you) I'm getting the attached error when trying to submit. My guess is that for some reason when the form loads that list box's first line is blank. And it doesn't like that empty space when trying to submit. There is a space above Cisco that data can be placed. The data type for the field in the form is not integer but text. Any idea on how to get rid of that space? After this I promise to not bug you for a long while. : )

Actually - see the error message? It says in it what the issue is - it is with the rowstamp field (see attached screenshot). Is that being set in the form anywhere? You may need to check with your DBA on this ...

I did actually see that, it's not being set in the form anywhere. But the reason I mention the empty field is because I did manage to submit the form twice but deleting that empty field (although for some reason it's not letting me do that anymore) also just to add some interger in there I put as default the now() function in that rowstamp field. And get the below error message which is also one I've seen on this form. The form cannot be submitted because it contains validation errors. Errors are marked with either a red asterisk (required fields) or a red, dashed border (invalid values). Field or group: frbny_bf_appdiscid Error: Only integers allowed

You'll want to take the now() function out of the rowstamp field. The only fields that will be submitted to the database are in /dfs:myFields/dfs:dataFields - the other fields that you've added don't seem to be required. I'd encourage you to drag the repeating group in the datafields onto your form to see what the values are after you run your query.

I did just that and I created a rule to run when Submit is actioned to fill in a hex code for that field. We don't use it so it shouldn't be a problem. It submits just fine now. Thank you so so much Hilary as always you have been a great help. I promise to get out of your hair now. : ) Have a great day.