You searched for the word(s): 2
-
Thanks for clarification. When I publish the form on sharepoint and fill it, clicking on save button (uses the code specified above), will put implicit transaction before and rollback after stored procedure call.
-
Is there a solution to publishing without the wizard? I wrote an new post earlier today:
I have a custom infopath form for the document information panel in Word. It has nothing to do with SharePoint and is being populated by a web service. The whole project is scripted for deployment. Therefore, I do not want to right-click --> deploy. I ...
-
Actually, the post I refer to, the second entry, he refers to the behavior of calling the stored procedure twice, once to generate schema. By "IP Query" I meant "InfoPath Query". I apologize for being unclear. What happens when you run your form and it actually calls the stored procedure? Is your data saved to the database?
-
I have a custom infopath form for the document information panel in Word. It has nothing to do with SharePoint and is being populated by a web service. The whole project is scripted for deployment. Therefore, I do not want to right-click --> deploy. I have not found a way to automate this. All I need is a way to publish to a local drive without ...
-
Sorry, I don't know what do you refer to as "IP Query" and can't find any similarity between my case and the one in your posting.
-
Give this tutorial from Office Online a try... It walks through creating a new form from a database as well as querying, submitting, etc.
-
I do know that when IP queries, the first query call will be to create the schema, the second query call with actually execute the sproc. This post has a little info on that.... When you test the form, does your sproc execute?
-
Just as a clarification -- default values are a field-based setting, not control-based. So the fields, which you see in your data source task pane, have default values, rules, validation and sometimes programming events associated with them. The controls, which you see in a view, on the form canvas, have things like size properties, conditional ...
-
Why don't you create the new form based off your database table? Then you'll be able to query and submit data to the database with your form. InfoPath supports this wil SQL or Access databases.... This article has more information -- the tutorial is for Access, but would be easy to adapt to SQL.
-
I've used InfoPath to merge the data into one xml file. (not completely cleanly- but I can address that later) I opened the XML file with excel and that allows you manipulate the data- pretty cool. But, so what? Now I want to produce reports, charts, etc. Any suggestions on products that do this well?