InfoPath Dev

InfoPath has limitations when creating direct connections to a database: http://office.microsoft.com/en-us/infopath/HP100950831033.aspx Quoting the article (I've underlined memo): None of the data fields in the main data source of the form store a large binary data type  InfoPath will disable the submit data connection if the ...

Here is a blog post that addresses your issue: http://www.infopathdev.com/blogs/david/archive/2007/08/29/showing-custom-modal-dialogs-in-managed-code.aspx It contains a link to source code for the custom message box winform.

Hey cocodog, Sorry for the late response... 1. There is bug in my deletion code. Here is the correct way to delete the nodes:// Remove existing values first List<XPathNavigator> nodesToDelete = new List<XPathNavigator>(); foreach (XPathNavigator citySourceNode in parent.Select("my:citySource", ...

Hello Takeshi, You are most likely experiencing a permissions issue. From what I understand, you are using InfoPath Forms Server and things work differently there for data connections. What happens when you preview the form from InfoPath Designer directly? You will probably need to convert your data connection to a UDC connection. I would ...

Mike, unfortunately, I think you're out of luck here: you cannot develop with VS2005 and IP2003. Here is a post which has more details on this problem: http://www.infopathdev.com/forums/p/5661/21207.aspx#21207

I think I have seen similar issues before. It could be an InfoPath bug, a possible workaround is to re-insert the code from scratch. The steps are: 1. Open your solution in Designer 2. Remove code (Tools | Form Options, Programming, "Remove Code" button), save as 3. Create a new VSTO solution based on your codeless XSN 4. Copy-paste the ...

I have created and uploaded a working sample here: http://www.infopathdev.com/files/folders/community_uploads/entry22603.aspx the zip file contains the ready-to-deploy XSN as well as the source code. I hope this helps you! David.

// You only need to do this once. This is needed because you are using prefixes. If you use other prefixes than dfs, you have to add other declarations in this line XDocument.GetDOM("Manual Procedimentos PROAF").setProperty("SelectionNamespaces", ...