Difference between read-only and print view in InfoPath

Learn what the difference is between a read-only view and a print view in InfoPath 2010.

ADVERTISEMENTS

A read-only view and a print view are two entirely different things in InfoPath.

A read-only view is a view on which you place controls that you want to make read-only, so that data is only displayed, but cannot be changed by a user through this view.

When you place controls on a read-only view, all of the controls become read-only, which means that a user will be unable to change form data through this view. You can make a view read-only by selecting the Read-only property of the view.

A print view is a view that is specifically designed for printing purposes. Often times when you place controls on a view, that view is not suitable for printing perhaps because you don’t want certain controls to have borders around them, etc.

In such cases, you can add and design another view that can be used specifically for printing purposes and then designate that view to be used for printing the original view used to fill out the form. The designated view is called a print view.

A read-only view can be used as a print view, but since print views are meant to be used when printing an InfoPath form, so should be removed from the Current View menu from which a user can select a view, you don’t necessarily have to make a print view read-only.

It is useful to familiarize yourself with and use print views in InfoPath, since they can come in handy when you want to perfectly layout your fields of your InfoPath form on a view that can be printed for example to PDF. See a demo video of using a print view for printing data from an InfoPath form on an image.

 
 Subscribe via RSS or Email

Copyright: This article may not be used on web sites (whether personal or otherwise), copied, disseminated, altered, printed, published, broadcasted, or reproduced in any way without an expressed written consent of S.Y.M. Wong-A-Ton. The techniques demonstrated in this article may be used within any Microsoft InfoPath project. This article is provided without any warranties. Copyright for this article is non-transferrable and remains with the author, S.Y.M. Wong-A-Ton.

InfoPath 2013 Cookbook: 121 Codeless Recipes for Beginners
InfoPath 2013 Cookbook 2: 121 Codeless Recipes for SharePoint 2013
InfoPath 2010 Cookbook: 101 Codeless Recipes for Beginners
InfoPath 2010 Cookbook 2: 101 Codeless Recipes for SharePoint 2010
InfoPath 2010 Cookbook 3: 101 Code Recipes for C# Developers
InfoPath 2010 Cookbook 5: Integrating InfoPath with Excel and Excel Services


Related Posts

ADVERTISEMENTS

InfoPath 2013 Cookbook: 121 Codeless Recipes for Beginners

InfoPath 2013 Cookbook 2: 121 Codeless Recipes for SharePoint 2013

InfoPath 2010 Cookbook: 101 Codeless Recipes for Beginners

InfoPath 2010 Cookbook 2: 101 Codeless Recipes for SharePoint 2010

InfoPath 2010 Cookbook 3: 101 Code Recipes for C# Developers

InfoPath 2010 Cookbook 4: 101 Code Recipes for VB Developers

InfoPath 2010 Cookbook 5: Integrating InfoPath with Excel and Excel Services