InfoPath Dev

I need a solution for creating electronic forms that can be accessed by multiple users via a browser.  I have used acrobat pro and find it simple to use but im being pushed towards Infopath.  My question is; will every user that wishes to access the form require infopath client in order to get full functionality out of the e-form?

InfoPath form templates work with InfoPath clients or with a webbrowser client through leveraging InfoPath Form Services.  A Web Server hosts the form, with some reduced functionality, for non-InfoPath clients.

You may also want to evaluate the Database Accelerator.  It has lots of features for adding functionality to forms via webservices and also includes a Form Viewer for displaying forms in a browser.

Qdabra Database Accelerator Suite Version 2.1 - Developer

 I would recommend using Pdf forms for SharePoint. Especially if you are on SharePoint 2010, then you even can use tools like pdfsharepoint.com. It allows designing pdf forms and fill-in forms using Adobe Reader. There are other Pdf forms solution also. InfoPath tends to be too complex for maintenance after form template is developed.

This is an InfoPath forum. We are all use InfoPath because it offers many features that PDF forms don't. Can PDF forms do XML without code? Can PDF forms submit to a Web service without code? Can you pull data from a database without code? Can PDF's write to SharePoint lists? Last time I checked the answer to all of these questions and more was a flat: NO. Wake up and smell the patchouli.

 Patrick,

 As a SharePoint consultant we use both InfoPath and Pdf forms when comes to implementing solutions. Both technologies have their pros and cons. When working with customers, we work very hard to set proper expectations about InfoPath and other technologies. Praising easy-to-use InfoPath does not do any good to this technology. In my experience the most dissatisfied customers (Microsoft related projects) were ones who insisted on InfoPath implementation. As a software developer I can use equally easy InfoPath or VisualStudio. The problems come when business requirements are reviewed, InfoPath usually requires С#/VB.NET development. As a result solution becomes no different than any other C# custom project. However, customers still live with expectations that their business users will support solution later. As InfoPath MVP you should agree that such situations happen more often than we wish. I would agree that it is all about proper expectations and it should be handler on all levels: executive meetings, requirement review sessions, and even infopathdev forums.

As of your pdf forms assessment: 

1. XML. Adobe LiveCycle Designer allows working with XML based data source without coding.

2. Web Service. Adobe LiveCycle Designer allows using data sources associated with web services

3. Pull data from SQL server. The same as above

4. Write data to SharePoint list. Yes. Actually many "yes". Adobe Acrobat X allows saving in SharePoint list. Adobe LiveCycle Designer allows using SharePoint web-services to upload document from any location. An integration 3rd party product (Pdf forms for SharePoint) allows bi-directional mapping of sharepoint columns to pdf fields.

Since I feel you might be skeptical to my claims, I include a link to Adobe Designer help: http://help.adobe.com/en_US/livecycle/9.0/designerHelp/index.htm?content=000546.html

I understand that it is an InfoPath forum. I believe in a balance view of every technology. InfoPath is a great tool when you have to implement forms fast and maintenance considerations are removed from equation. InfoPath is also good when you need a quick integration with SharePoint workflow (or even advanced 3rd party workflow tools like K2[blackpoint], Bamboo workflow, Nintex Workflow, etc).

P.S. I don't like smell of patchouli. I prefer basilic. 

Thanks for the response and sorry for being a bit flippant, but I sensed (incorrectly) that you were advertising your product.

Based on what you say, it does seem that Adobe LiveCycle Designer has improved significantly since we last reviewed it over a year ago. I will try to make a point to review it again. I seem to recall that the XML support was also quite limited in PDF since it was something that Adobe added to the product later (the product wasn't built around XML to begin with).

I agree with you about the need to keep an open mind on these technologies.

Your statement that InfoPath usually requires code isn't true though. We have developed hundreds of complex forms that do not require code. For the remaining ones that do require code, we provide qRules which is a common library plugin.

InfoPath can be a very very low maintenance solution if a) data-driven Web services are used (such as Qdabra's XML Web Service suite, called DBXL), and b) common libraries are used like qRules to fill gaps in the client. qRules does the bidirectional mapping to SharePoint lists, etc. There's a free trial and it's only $199 to buy. What does Pdf Forms for SharePoint cost?

Patrick.

I appreciate your feedback on InfoPath 3rd party tools also.

Thanks.