InfoPath Dev

Hi Bob, Judging from the following blog, it looks like it's just oEnvelope.CC.  http://blogs.msdn.com/infopath/archive/2004/08/17/216172.aspx

Hi sboyddyn and welcome to the forum!  You were so close!  Try this: normalize-space(preceding-sibling::Flight_Leg[position() = 1]/@To_Airport)   I have attached a sample I came up with to figure it out.  Hope this helps!

Hi Justin,  I don't think you're problem is actually in adding the nodes to the XML, but displaying them in the view. Do this experiment:  Delete the repeating table from the view and run your code again. To remedy this, you can use some visual tweaks to make sure InfoPath is only displaying a few rows at a time.  20 or ...

Here is another tutorial on submitting list items to SharePoint: http://www.infopathdev.com/blogs/matt/archive/2006/02/02/Add-SharePoint-List-Items-with-InfoPath.aspx

Also, be sure that you are not URL encoding in your concat()... Let InfoPath do that itself.

Hi alex350r, Before you go writing your own custom web service layer, have you seen our DBXL product? It provides a generic web service layer that you can use to translate infromation from the InfoPath client in the the database, and then back again.  On top of this core functionality, there are a slew of other features that allow rapid form ...

Everything is stored in the content DB, but you should be able to get it out via the SharePoint web services.  The XSN and the XML files are both serialized to binary and then stored in the Content DB.  At least, that's my understanding...

Thanks for the info, Ernesto!  Do you know when intelligent is going to be fixing this bug?

Hi cocodog123, This is weird.  Do you happen to check the status after the first button click to make sure that the changes are saved and it just takes some time for you to see them? Are you doing any kind of logic on the B node when you click Save?

Hi joshie777, These filters are very difficult to debug.  I would really have to see your schema to give better advice, but I would take the first clause out (before the and).  It seems unecessary and will cause the expression to evaluate to true more often than you like.