InfoPath Dev

Thanks Patrick .. that does answer my question!

Here is a recent thread with a similar question.

Hi, I have recently followed a tutorial for publishing forms by email which can be opened in Outlook 2007. I got the impression from this that the user didn't need to have infopath as well. However, the user has been unable to open the form in Outlook 2007. I have gone back through my settings and I have signed the form and given it full ...

  Hello, I have Exp infopath form with custom workflow. I want to archive infopath data into sharepoint custom list as well as SQL Server 2005 once my workflow get completed. Please suggest best practice to implement above scenario.   Thank you.

  I have developed custom multilevel approval workflow. For the same i have taken following steps: Project created: 1) ApprovalWorkflowFeature (Its contain content type fields _AprrovalStatus and _ApprovalNotes). 2)CustomApprovalForms (ApprovalForm.aspx) 3) Multilevel Approval Workflow (Business Logic). Workflow get start when new item ...

Hi Catharine, We've come up with a fix for the issue you're having and it's documented here. Basically, the latest DBXL v2.4 now has a "Content Type" option in the SharePoint mapping tab. You should be able to quickly map your content type using that option by following the steps in the blog.  You may download the ...

Hi, thanks for your reply ,,,,,,,doh !!! yes it is but when I change it to another value my dropdown box does not show any data, ie if I change value from "ID" to "Code" then preview form it shows me nothing , so im assuming my rule could be wrong, or am going totally in the wrong direction here ? 

I have created this certificate myself, it has been working fine until now. I attached the picture of the security warning. This feels very weird, I don't think you're supposed to see that kind of dialog box ever... I have a strong feeling it has nothing to do with InfoPath only.

Thanks for replies and suggestions. I will test this today and report back.

You  need to construct your SQL query in a manner that is syntactically correct.  In this case, it looks like just tacking a WHERE clause on the end of the default SQL statement isn't going to work.  Why don't you figure out what the entire query is supposed to be and use that instead?