InfoPath Dev

^Sure.  In my project, I forgot that the approver did not need to be able to edit the form (meaning they did not need to open the form up in the InfoPath 2003 client with a Contact Selector in the form) so having a "view" of the form in the body of the email was sufficient. This has given rise to new ...

I attached a screenshot of how the form appears in Outlook 2007 after it has been submitted using the Email Submit data connection and all controls have static widths. Does anyone know how to fix: a.) Fields get shfited down b.) White space below "Comments" c.) The form is still wider even after I gave all ...

Currently testing if giving the fields a hard number as a size fixes this issue.

I have my submit using the Email Submit Data Connection and the following setting: "Send only the active view of the form and no attachment" The body of the email contains the active view of the form, however the formatting of the form widens considerably when viewing the email using Outlook 2007.  The form in ...

Thanks Mr. Cobb, I figured as much.  We have devised a new solution so this issue is not crucial to me anymore at this point.

An InfoPath form saved as 2003 containing a Contact Selector cannot be opened in InfoPath 2003.  Basically, I was wondering if someone could provide me with a link so that I could add something similar to a Contact Selector using InfoPath 2003. Thanks

Yup, I just want GetErrorCount at this moment.  I forgot to mention that I get an error when I run the Injector.  Here's the log: removed the trustSetting attribute Adding a file reference to Qdabra.Tools.RulesLibrary.dll Adding a file reference to QdabraRules.xml Adding a file reference to QdabraRules.xsd xsf2:managedCode node ...

I am trying to get the get error count from qRules but I get an error when I try to make the data connection to the DbxlDocumentService.  "The file is not a valid XML file. The form contains XML that cannot be parsed: A string literal was expected, but no opening quote character was found. Line 19, Position 38   <TABLE ...

Wow you are fast!  I was about to delete my post as I have fixed my problem.  It turns out that the manifest.xsn is not the only file you should search for the Data Connection name as I found the reference in my view1.xsl file.

I am suffering from the same situation.  It was caused when I removed the Data Connection Receiving from a SharePoint library.  I have executed the steps recommended (checked the logic inspector for references to fields/groups coming from the data connection, anaylzed the manifest.xsn for references to the Data Connection and to ...