In the main system window items of pull-down GDB menu allow performing operations which either belong to geoinformation database as a whole, affect all database components or control ObjectLand work without reference to some particular databases.
Open – opens a dialog for selecting the current (opened) GDB. The operation of opening GDB was described in detail in previous chapters.
Close – stops work with the current GDB. Before opening some other database it is possible to work only with shared style library.
Merge – permits merging all or part of the components of two different GDB.
Properties – opens a property sheet “GDB properties” enabling the user to browse information about the files size of the current GDB, permissions of the current user to GDB and about some other GDB characteristics.
Create – allows creation of a new originally empty GDB and assign a name to it.
Rename – permits assigning a new name for GDB.
It is not possible to rename the current GDB.
The presence of two GDB which names differ only by numbers “0” or “1” at the end (for example, CITY and CITY1) in one folder is not allowed. It is connected with the rules of composing GDB file names. When performing an operation of creating and renaming GDB the system tracks the process to prevent the appearance of two such names.
Reorganize – performs the operation of GDB reorganization.
This operation is used to increase efficiency of the system work with the given GDB but does not affect the work results.
It is impossible to reorganize the current GDB, it should be closed before this operation.
Update – is used to transform GDB created using old ObjectLand versions to the current version format.
It is impossible to update the current GDB, it should be closed first.
Check Integrity – allows performing integrity check of GDB or shared library structure.
It is impossible to check data integrity of the current GDB, it should be closed first. For checking data integrity of the shared library there is no such limitation.
If the GDB for which the integrity is checked is opened by another user, an access error occurs during checking.
Repair – permits an attempt to repair GDB or shared library integrity which has been broken.
It is impossible to repair the current GDB, it should be closed first. For repairing shared library it should be either closed (that is, ObjectLand should be started without using shared library) or opened in the exclusive mode.
Consolidate – serves to perform the operation of consolidating changes in the GDB the work with which was organized in the change file using mode.
It is impossible to consolidate the changes in the current GDB, it should be closed first.
User – serves for changing the current GDB user.
The system opens a dialog “User name and password”. After entering correct name and password and pushing OK button the system marks the change of the current GDB user and sets permissions assigned to this user.
Print (or Print structure) – performs printing of selected GDB component. The command action depends on the type of the selected component.
Settings – opens a property sheet “ObjectLand settings” serving for assigning different parameters of the system settings.
Menu items with the names of the last opened GDB (history list) permits avoiding search of these GDB on a disk in case of their repeated opening. Together with the name, the used GDB open mode is stored.
Close – stops the ObjectLand sessions, closes all the system windows.
It should be noted that many operations with GDB described above cannot be performed with the current GDB. The following operations can be named here: renaming, reorganization, updating, integrity check, repair and consolidation of GDB. When attempting to perform one of the enumerated operations with the current GDB the system generates a message shown at figure 6-1.
Figure 6-1. The system message at inadmissible operation with GDB
Analogous situation occurs if the present GDB is opened by some other user even if it is opened in shared access mode.
To perform an operation with GDB all the users should close this GDB. After completing the operation, GDB can be opened again (for example, using history list).
 |  |
