A view represents any type of database object that has rows including tables, queries and stored procedures.
| Option | Description |
|---|---|
|
A user-friendly name for the view. If a caption is not specified, the actual name of the view is used. | |
|
The field that serves as the unique identifier for each row in the view. Gatsby requires each view to have a single field that serves as a key. The field that Gatsby has derived as the key field is displayed in angle brackets (<>). For tables, Gatsby derives the key field by analyzing the index structure. This usually produces the correct key field unless your table has a multi-field key or does not have a key defined. For queries and stored procedures Gatsby will not be able to derive the correct key field unless it participates in the many end of a relationship. | |
|
The set of fields that uniquely identifies a row to a user. For instance, a table that contains information about Employees might has a numeric key field like EmployeeId. While this works well as a key field, it does not provide a user friendly description of the Employee. A more suitable row caption would be the name of the Employee. For tables, Gatsby automatically determines which set of fields will serve as the row caption by examining the index structure of the table. The preferred index will be unique, non-primary and contain text fields. If Gatsby cannot find a suitable index, it will use the first field. The Gatsby derived row caption is displayed in angle brackets. You can explicitly set the row caption option to be any field in the view. | |
Determines whether a view is displayed at the top-level of the Relational Navigation View. Dependent views are never shown. | |
|
Dependent or weak views depend on the existence of some other view. For instance, an Order Item cannot exist without an Order so the Order Item is dependent. Dependent views appear as sub-forms on the sub-forms and do not appear in the Relational Navigation View. Gatsby automatically determines a table to be dependent if it is on the many end of a cascade-delete relationship. You can override the Gatsby derived value using the dependent option. | |
|
Description |
A user friendly description of the view. |
For Microsoft Access databases Gatsby saves the overrides as properties on the database object. The description property corresponds to the Microsoft Access native description property.
For other databases, Gatsby saves the overrides with the data sources file.