Re: InfoPath vs. SharePoint lists

eddyblanco — Tue, 05 Jan 2010 22:56:33 GMT

InfoPath vs. SharePoint lists. Infopath is a form and Sharepoint list think of it as a DB table(just store information). You could modify the taxanomy and make a presentable form, but I would just use Infopath as the form and the list to save the information. Also if this is going to be an external site you will need to use Form Services.

InfoPath vs. SharePoint lists

jm123 — Tue, 05 Jan 2010 20:53:41 GMT

I'm just getting started with InfoPath and SharePoint and am trying to figure out how and if each applies to a project I'm working on.

My organization would like to setup a very basic e-commerce web site that handles registrations and payment of fees for courses. An anonymous user (there will be no user accounts) fills out a form with their personal information and the course they'd like to attend, are then forwarded to a separate site to complete the payment, and are then returned from the payment site with a success/failure flag which needs to be recorded along with the data submitted by the user.

I'm wondering if there's any reason I should use an InfoPath form over a standard SharePoint list. Further, if InfoPath forms that are filled out and submitted by the user are saved as files on SharePoint, is it possible to view all the data from all the forms in tabular format (rows/columns)? Is that just a matter of creating different views? Does an InfoPath form essentially define a table in the database sense?

One other requirement is that this will all be over the web (we have InfoPath services on our SharePoint server) and I'll have to apply my organizations look and feel to the page the form appears on.

Thanks.

Newbie Questions

Re: InfoPath vs. SharePoint lists

InfoPath vs. SharePoint lists