Hi Navid,
Are you using InfoPath 2007 or InfoPath 2003? Do you know if you are using the new object model in 2007 or not?
For universal data connections, the SelectCommand has the following structure:
<udc:SelectCommand>
<udc:ListId/>
<udc:WebUrl/>
<udc:ConnectionString/>
<udc:OperationName/>
<udc:ServiceUrl UseFormsServiceProxy=""/>
<udc:SoapAction/>
<udc:Query/>
</udc:SelectCommand>
For a Web service submit, you only need to specify the ServiceUrl and SoapAction. For example:
<udc:SelectCommand>
<udc:ListId/>
<udc:WebUrl/>
<udc:ConnectionString/>
<udc:ServiceUrl UseFormsServiceProxy="true">
http://formsboard.com:30794/dbxl/dbxldocumentserviceEx.asmx</udc:ServiceUrl> <udc:SoapAction>
http://qdabra.com/webservices/SubmitDocument</udc:SoapAction> <udc:Query/>
</udc:SelectCommand>
There should be parallel properties when you set up the data connection in code (vs. UDC).
I hope this helps you. Good luck.
I thought SelectCommand contained info on connection string and SQL query to perform. For Web services, you shouldn't need it.