Other Objects

The data-banks contain a large variety of objects and object types in addition to those mentioned above. When it comes to names of these objects the user may either give them arbitrary names or they may get fixed names by AVEVA Marine that the user is never really confronted with.

Examples of the former category are drawings and nestings. However, it is recommended that a customer sets up rules of his own for how these objects should be named. But this is nothing that is required by AVEVA Marine.

Examples of objects with fixed names are miscellaneous set-up tables for design standards. AVEVA Marine assign fixed names to these objects and they have been selected with a structure to minimize the risk for name collisions.

Finally, there is one very important (and general) aspect on names of objects in the data-banks. Names of objects that may be processed simultaneously by a AVEVA Marine program must have unique names. Otherwise AVEVA Marine will in some cases issue an error message but in other cases the result may be errors that are difficult to penetrate and there is also a risk to get corrupted objects.

For example, it is quite possible to give a drawing the name of a block because these objects are stored in different data-banks. If, however, a view is generated in a drawing via the block object with the same name then problems will occur. When the block is read into the work area of the program to be sequenced for panels to be included in the view (drawing) there is already an object (the drawing) with the same name and this causes problems.