You can perform a variety of tasks to manage views, similar to those that you perform to manage tables, table fields, and table records, for example:

• Specify captions for view fields.
  
  
• Add comments to views and view fields.
  
  
• Specify default values for view fields.
  
  
• Create validation rules for fields and records.
  
  
• Create indexes on view fields using the INDEX command.
  
  

  Note:
  Unlike table indexes, indexes you create on views are not stored and are removed when you close a view. Consider the size of the view's result set before creating an index. Indexing a large result set might decrease performance of your view.

• Create temporary relationships between views or tables and views using the SET RELATION command.
  
  

  Tip:
  To increase performance when using the SET RELATION command, make the view the parent and the table the child in the relationship.

  Note:

  Making the table the child is more efficient because the structural index of the table is constantly maintained, quickly accessed, and can be used by the data environment to order the records. In comparison, the index on the view must be rebuilt each time the view is activated and takes more time than the index on the table. An index on a view is not part of the view definition; therefore, if you use a data environment, the view cannot be the child because the index on the child must exist as part of the definition.

In This Section

Related Sections

Send comments about this topic to Microsoft. В© Microsoft Corporation. All rights reserved.