Hi,
In order to fill out forms created in InfoPath with all of the rich-client
functionality and data validation available in that environment, users will
need a copy of InfoPath installed on their workstation. InfoPath provides a
rich user experience that goes beyond what you normally get with a
Web-based form. For example, InfoPath provides data validation for the form
as the user fills it out. Validation can detect errors at the schema level,
through logical constraints, and even through script. This validation
occurs immediately, so the user doesn't have to submit the entire form
before finding out there's an error.
InfoPath also provides conditional formatting, so your form can be more
responsive to user input. For example, you might have a field that changes
its background color to red whenever an unusual (but not illegal) value is
entered. Again, this occurs as soon as the value is entered, so the user
has a chance to react appropriately. InfoPath provides the ability to work
on a form offline, or to interrupt work on a form and come back to it at a
later time, something web-based forms simply can't offer. InfoPath can
easily make use of SQL Server and Access databases, and existing XML files,
in addition to Web Services, without having to write low-level code.
InfoPath also provides the ability to easily merge the data in multiple
forms into one document. This is a powerful ability and one that customer's
really like.
However, there may be times that you don't need this rich functionality.
The data in an InfoPath form is saved in standard XML format, so you can
access the data with just Internet Explorer or Notepad. You can create an
XSLT transform that converts the XML data into standard HTML for viewing
(or use the View*.XSL transforms that InfoPath creates). See the following
KB article:
826990 How To: View Transformed InfoPath Form Data in Internet Explorer
http://support.microsoft.com/?id=826990
The ability to extend InfoPath 2003 scenarios "outside the firewall" (e.g.,
government to citizen, government to business, business to business, etc.)
and/or deploy InfoPath to more people more easily is feedback we've
frequently received. This speaks to the great value of the InfoPath client
- and the desire for it to address an even greater number of business
processes. We are considering ways to enable these types of scenarios in a
future release of InfoPath.
It is important to note that it is possible, today, to build browser-based
solutions based on InfoPath forms. For example, you can build a solution in
InfoPath (building a schema and Web services) that can be used for
collecting information within the firewall, then use the same schema and
Web services for building an ASP.NET solution for collecting information
outside the firewall. For business solutions that require a "reach"
(browser-based) solution, yet still use the power of InfoPath for the parts
of the process that occur within an organization (where InfoPath can easily
be deployed), there are two options:
- Use ASP.NET forms in the solution to front-end the process. Data is
gathered in the browser-based forms, and then moved into the InfoPath forms
where available. This combines the reach experience for initial data
collection and the rich experience of interacting with that information via
InfoPath. Customers can use the same schema and Web services for both the
InfoPath and ASP.NET solutions.
- Work with one of the many partners that have developed solutions based on
InfoPath including Sourcecode, Teamplate, Ultimus and Cardiff.
Lastly, under the terms of the licensing of open and royalty-free XML
schemas for Office (including InfoPath), companies can create a
browser-based offering (or even a rich client, if desired) compatible with
InfoPath. See
http://www.microsoft.com/mscorp/ip/format/ for more detail.
I hope this helps!
Best Regards,
Scott L. Heim
Microsoft Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
