Designing a browser-enabled InfoPath form that can store data in a database - Part2

re: Designing a browser-enabled InfoPath form that can store data in a database - Part2

Sebastian Wagner — Wed, 21 May 2008 17:29:47 GMT

Hey!

did you ever tried your post?

In my case the "Convert" button is disabled after creating the data connection to SQL server. If I use a SharePoint list for receiving data, the convert button is enabled. Unfortunally my informations are stored in SQL server - so why is the button "Convert" disabled?

re: Designing a browser-enabled InfoPath form that can store data in a database - Part2

eterenzi — Thu, 22 May 2008 10:19:34 GMT

I wrote the post based on a project I actually did, so yes I have tried my post.

The convert button is disabled if you have already converted the data source to a udcx file. Just try to recreate the data source connection with the database and then you should see the Convert button is enabled.

re: Designing a browser-enabled InfoPath form that can store data in a database - Part2

pc forum — Sun, 21 Dec 2008 19:57:16 GMT

Great post, explained really well and I could really understand. Thank you.

re: Designing a browser-enabled InfoPath form that can store data in a database - Part2

Mindblown — Thu, 08 Jan 2009 19:16:34 GMT

Great Post, got the example to work perfectly. Looking for a solution to be able to submit to several tables in one go. Any suggestions please?

re: Designing a browser-enabled InfoPath form that can store data in a database - Part2

Perry — Wed, 14 Jan 2009 16:27:58 GMT

When you delete the data connection for the "Retrieve Shop Data" Button , what connection do you use to retrieve the data. I am assuming when you input the shop id and click Retrieve the name/address/pwner will come up.

re: Designing a browser-enabled InfoPath form that can store data in a database - Part2

eterenzi — Wed, 28 Jan 2009 00:47:26 GMT

Perry

The connection you use is exactly the same connection but this time we are using the one we have just saved on sharepoint (instead of the one local to the infopath form) so that now the connection is managed centrally: if something changes to the DB and the data connection is modified accordingly, as long as the same interface is used and the name of the data connection is preserved, our form will still work.

re: Designing a browser-enabled InfoPath form that can store data in a database - Part2

eterenzi — Wed, 18 Mar 2009 17:35:04 GMT

Mindblown:

you could modify your webservice so that the stored procedure updates more than one table.

re: Designing a browser-enabled InfoPath form that can store data in a database - Part2

Ivan — Tue, 14 Apr 2009 21:15:22 GMT

I followed all your steps and can't seem to get it to work right. I get the following message:

One or more data connections in your form are specified with a server-relative link, but no publish location has been defined for the form. Data connection settings will be retrieved from the server specified at design time. To enable the server-relative link, publish your form to a Microsoft Office Server. Certain types of server-defined Web Service connections will not work with the design time settings.

I also get this message:

The query cannot be run for the following DataObject: Classes

InfoPath cannot run the specified query.

The query cannot be run for the following DataObject: Classes

InfoPath cannot run the specified query.

You are working offline. InfoPath will use offline data instead of connecting to external data sources. If no offline data is available, some form elements, such as drop-down lists, may be blank.

I get this message even though I have published the template to SharePoint. Any clues?