Oct 13, 2007 at 08:16 o\clock
InfoPath Forms Services provides functionality that enables both Office administrators and users to deploy browser-compatible form templates. InfoPath form templates (XSN files) created in the design mode of the InfoPath program can be published as browser-enabled form templates that can be opened and edited in a Web browser from servers running InfoPath Forms Services. This enables you to expose full-featured forms to users who do not have the InfoPath program, such as customers and partners.Form templates that contain business logic (such as a compiled, managed code DLL), require full domain trust, or use a data connection that is managed by an administrator must be deployed by an administrator. Because of the potential for security, performance, and manageability issues, it is important that these form templates are thoroughly reviewed by an administrator prior to deployment. You can manage these form templates on the Manage Form Templates page on the Central Administration site.To deploy an administrator-approved form template, you must complete three actions after the form template has been designed: verify, upload, and activate . These steps can either be performed through the command-line interface or through the Central Administration site. You can upload a form template by using the Publishing Wizard in the InfoPath program, using the command line on a server running InfoPath Forms Services in the farm to which the form template will be deployed, or by using the Central Administration interface. As the farm administrator, you typically receive from the form designer a form template that is already prepared for deployment.Site definitions are composed of multiple files located in the file system of each Web server. Site definitions and templates work together to customize a site. Custom templates are always associated with the site definition on which the template is based. A custom template depends on the base site definition in the file system in order to work. A custom template is the difference between a site definition and the state of the site after a template is generated. The template tracks changes to the site definitions that are stored in the configuration database. This article describes the advantages and disadvantages of using custom templates and site definitions and provides guidance about when to choose one over the other, and how to avoid overwriting custom templates and site definitions when installing product updates.There are two ways you can customize SharePoint sites. You can use custom templates or create site definitions. Custom templates enable you to customize a site by using the user interface (UI). For example, you can derive a custom list from an existing list, or create a custom list to use as a list template that Site Administrators can choose from a list of available list templates. Windows SharePoint Services stores all custom templates in the content database. You can customize list and site templates from Top-level Site Administration or by using Microsoft Office FrontPage 2003. For more information about using FrontPage to customize SharePoint sites and portals. see:http://www.sharepoint07.com 
