InfoPath Dev

Entry level Infopath designer here with a basic question.   I've created an Info Path form to collect data in the form of a survey (basic survey questions about training classes).  I want the students to be able to fill out the survey (mostly option buttons and drop down questions) and submit the form when complete.

I'm struggling to find a method that allows me to capture the data they enter in the form.  I've been reading thoroughly through "How-To's" and forums and I'm overwhelmed with the options (Access, SQL, Qdabra, web-based, Sharepoint, etc).   I really want to keep this simple.  What is the easiest way to give users access to the form so they can fill out, submit, and I can collect the data?  All users are on the same network, so a shared Access DB may be the easiest way?  I realize I may have to redesign my form through the data connection wizard, which I am fine with. 

I get really confused when you start talking about secondary DB and parent/child relationships of the tables, etc.  I'm also working deligently to learn this on my own and I've created a form through database wizard connected to a sample access DB and when I go to bind a text box for submitting data I get "You have chose to bind a non-repeating control to a repeating field or group".  Am I taking the wrong approach with the Access DB?    Any direction would be much appreciated.

 Thanks,

 Kevin

Hi, Kevin:

It can be confusing. If you have SharePoint available, and don't need to create any real reports off your surveys, you could use your InfoPath form and publish it to a SharePoint form library and have your users fill it out there. Of course, if you have SharePoint, you may just want to create a SharePoint survey -- they have some nice features: http://office.microsoft.com/en-us/sharepointtechnology/HA011612251033.aspx

If you do not have SharePoint available, then you may want to rebuild your form off a database in Access. That way you have the built in submit functionality. When you go to connect to your data source, after the table is displayed in the data source structure, you can click Modify and you will see a checkbox for Multiple Records (at least in IP 2007, I don't remember about 2003). If you deselect this, your group for your table data won't be repeating. You can then add your controls, binding them to the data fields in the data source. Here is an article from Office Online you may find helpful: http://office.microsoft.com/en-us/help/HA011032471033.aspx

Let me know if you need more information or help, okay?

Thanks for the quick response, Hilary.  Sharepoint sounds like it has some great features, and as our demand for forms and functionality of those forms grow, it will be something I need to implement anyway.  I'm going to look into Sharepoint and see how invloved it is to set it up.  I'm not even sure if I have to buy it or if it's just a component of Windows Server 2003, I will need to do some research.

 I will also test the alternative solution you mentioned about unbinding the multiple records for repeating data and see how that works.

A lot depends on what you are comfortable working with.

My background is SQL and that is what I use exclusively.

Provides a tremendous amount of flexibility in using the data.

I'm a little confused on the whole Sharepoint setup, are there any articles that you know of that describe the setup of publishing forms through Sharepoint Intranet available?

I've downloaded and installed Sharepoint Services 3.0 and it is up and running.  Now I'm reading something about MS Office Sharepoint Server 2007 (which apparently is different than Sharepoint Services 3.0) and also must be purchased and licensed.   Can I still accomplish what I need using the free Sharepoint services that I already have installed?

You can publish your forms to WSS 3.0 sites. You don't have to have MOSS. http://office.microsoft.com/en-us/infopath/HP010967231033.aspx has information about publishing forms, and this has more on submitting forms http://support.microsoft.com/kb/826993.

You may also wish to use a form library -- here is some more information on that: http://office.microsoft.com/en-us/infopath/HP010968041033.aspx