Data can be viewed in the main window. IJC currently supports two View types, the Grid View , which emphasizes data display from a single database table, and the Form View , which gives more focus to a single record within an Entity. Views belong to a Data Tree, and multiple Views of a Data Tree can be open at the same, with content selection automatically being synchronised between Views. Similarly, if you run a query or change the sort directives then all Views belonging to that Data Tree will update.
1. Grid View
The Grid View allows your to view data in a tabular fashion. It is similar to a spreadsheet. The data is organised strictly in a row and column paradigm. Unlike many tools, very large set of structures can be viewed and rapidly scrolled in the Grid View.
2. Form View
The Form View lets you design a form that displays your data. You add display Widgets to the Form, and bind them to particular Field(s). Each Widget can be re-sized and re-positioned, allowing you fine grain control of the design. Relational data can be displayed, with the contents of the Widgets updating to reflect the current content and selection.
One of the Widgets that that can be added to a form is the same Table Widget that is used in the Grid View. Thus the Form View can be thought of as a super-set of the functionality from the Grid View. However it is more complex to use.
Which View to use?
Use the Grid View if:
Use the Form View if:
To open a view, expand the Data Tree node
(
) in the
Projects window,
then double-click either a grid view node
(
),
or a form view node (
).
Alternatively, choose Open from the view node's right-click menu.
The selected view appears in the main window.
To create a new view for a selected table, right-click a selected Data Tree node
(
) in the Projects window and choose
Add View. The New View dialog opens:
When working in a view, supported functionality includes:
Unlike most of the other artifacts that you deal with in Instant JChem ( Schemas, Entities, Fields, Data Trees etc.) which are shared between all users, a View belongs to an individual user. This means that you can make whatever changes you want to a View, and you will not affect other users Views. This is important when using a remote database in multi-user mode, where each user only has read-only access to the core data model components, but will wish to create and modify their Views, even if they can't modify the underlying model or the data within it.
IJC allows views to be shared between mulitple users in two distinct ways:
Copyright © 1998-2008 ChemAxon Ltd. All rights reserved.