views.pdf - Anygraaf Neo System Configuration Guide Views Views By views we mean here objects that are used by Anygraaf applications to display a wanted

views.pdf - Anygraaf Neo System Configuration Guide Views...

This preview shows page 1 - 2 out of 17 pages.

Anygraaf Neo System Configuration Guide Views Views By views we mean here objects that are used by Anygraaf applications to display a wanted subset of data in a window in a specified format. Each view is an entry in the BT_SQLSTATEMENTS table. These views are not created at the database level with a CREATE VIEW statement, nor do they provide any database-level access restrictions. To strictly limit access to data based on database roles, the “SQL view” mechanism is available; for details see the UserManager documentation. Views can be opened in the Neo application as workspace windows. Views also appear in the menu of the Search button in dialog boxes. Views have several user interface settings, whose meaning can be found in the UserManager documentation (View dialog and BT_SQLSTATEMENTS table). This document concentrates on how views can be organized, how to write the SQL statement that defines the view, and how to define a dialog box for getting search parameters from the user. The reader is assumed to have basic knowledge of the SQL language. A view can have default values for objects that are created through the view; the syntax of these is described in document Default values . Organizing the views Each view is linked to a single entry in the BT_CLASS table. This defines the main table of the view, it is the table that the view “belongs” to. The view can display data from several tables linked to the main table, but when items are added, edited, or deleted using the view, the main table is that table to which the editing operations apply. For item management in a view to be possible, the view must return a column containing the ID values of the main table; this ID column is hidden and most often does not have to be included in the view definition. BT_CLASS has an additional entry named _MULTITABLE_; this makes it possible to define views that are not connected to any particular table. Views can be organized both in a tree structure and in linear ordered lists. The tree is formed by setting views as parents of other views. Views that do not have a parent form the root level of the tree, their direct children form the next level, and so on. Each view can be assigned an order number (ORDERNUMBER column in BT_SQLSTATEMENTS). The ordering is independent of the tree structure and is used in the following places: The Search button in dialog boxes shows all the available views of a particular main table, and these are ordered by the order number. The New search button in the Neo application has a menu showing views that are available for filtering the contents of the currently active view. This list is ordered by the order number, and the first view in this order is used when the user clicks the button without opening the menu or presses Ctrl+F.
Image of page 1
Image of page 2

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture