Vencor Software

  • Home
  • Products
  • Resources
  • About

StudioWorks

  • Overview
  • Features
  • Community
  • Referrals
  • Training
  • Consulting
  • Manual
  • Buy

StudioWorks - Features - Meta-Data

The schema classes in Omnis are used to map list and row variables in your application to the SQL database. Each schema class is mapped to a database table and the schema class columns are mapped to database table's columns.

The Omnis schema classes keeps track of the column name, datatype, whether on not the column is a primary key column, and whether or not null values are allowed. However, the Omnis schema classes are NOT able to keep track of whether or not the column is indexed, if it is a foriegn key and if so what table and column the foreign key references, and other column constraints.

The StudioWorks SQL Meta-Data Editor allows you to store addition information (meta-data) about each schema class column. The meta-data is kept in a row variable which is stored in the '$userinfo' of each schema class column.

The StudioWorks SQL Meta-Data Editor not only stores database meta-data, it also stores GUI meta-data. The GUI meta-data allows you to preset if and how the column will be displayed in lists and entry fields, when and how users can edit the field, whether to include the field in prompts, default sorting, etc. Even the label, tooltip, and abbreviation (for list and report column headings), are stored with the GUI meta-data. Storing the label and tooltip text in the meta-data ensures that where ever the column is displayed in a window or on a report the label will be consistent and if it is used in several windows you only need to change it in a single location.

Copyright © 2007 Vencor Software