InfoPath Dev

Ok you probably use vb2007 try MainDataSource.CreateNavigator().SelectSingleNode("xpath", NamespaceManager).Value I notice that your xpath is probably bad it must look like something like :/my:myFields/my:Field1

The first thing I would check is the data connection and the unique name. If the unique name (email and date time stamp) is getting updated when the second user edits the document, then that would explain the new record in the library. The unique name must only be set when the document is first created, and the data connection set to allow ...

 We are currently facing the similar problem ... did anyone food a solution for it?  Kind regards, Wim

Hi. I have one content type used under multiple libraries. I would like to be able from code behind of this content type 1. find the name of library the content type form is used in currently (opened in) 2. based on previous fact, populate either expression box or header or footer or text box field of this content type ...

I am downloading an Infopath form as an xml string from IIS and want it to open in Infopath. I set the ContentType to "application/ms-infopath.xml" (not sure where I got that from). On some machines it is fine, on others the xml opens in the browser, or in Visual Studio or some other xml editor, even though Infopath is ...

Having wasted a day and a half messing around with code on this, I found out that if I set the Default Value for the field in Tools>Default Values then it works. Could anyone explain the difference between setting the Default Value here, and setting the Default Value in the Data Source taskbar?

I see, thanks for the link Patrick. However, is it possible to refresh the DocID on a form I sent out as an email? Reason is because my form is using DocID for versioning. I used a generated GUID to identify my forms before they are sent out as emails to recipents. On receipt and opening the form, the recipent now has a form of higher DocID ...

Wow, that is esoteric. I'm assuming it is not the default. Anyway, nice job slaying the dragon.

Hi Alf Kiil, We implemented this several years ago and have a working sample for both rich client and browser forms. I will ask one of our developers to respond to your specific question tomorrow. More soon,

Well, SharePoint document IDs are bad because they don't migrate to other systems. I strongly recommend using a GUID or a unique Key that you construct in the form's logic on submit. We used DocIDs for many years and finally adopted a policy of using Keys for all of our solutions. They're easy to create and they are better than DocIDs ...