Miscellaneous Error Messages

This lists all non-Analyze Visible Analyst Workbench error messages and their explanations. The error messages are listed in alphabetical order.

Note

Error messages are in absolute alphabetical order: For example, if the message begins with "The", then it is alphabetized under "The", not under the first important word.

You can also press [image] to get a listing of error messages.

Choose the first letter of the error message on which you want Help.

A	B	C	D	E	F	G	H	I

J	K	L	M	N	O	P	Q	R

S	T	U	V	W	X	Y	Z


A

A change is pending for this diagram -- Cannot edit.

A class must be labeled before a Nest operation can be performed.

A couple may only be changed into another couple type.

A diagram is being inserted into the tree -- This branch cannot be altered.

A non-couple cannot be changed to a couple.

A non-loop may not be changed into a loop.

A process must be added to this context diagram.

A process must be labeled before a nested decomposition can be performed.

A Program can only have one item as the root module.

A relationship can be labeled only when two NAMED entities are attached.

A supertype/inheritance relationship already exists between this pair of objects.

A supertype/inheritance relationship cannot be recursive.

A supertype relationship cannot be used with a non-fundamental entity.

A tree file for project "X" is damaged or missing.

A user-defined object cannot have the same name as a VAW entry type.

Access denied -- another user is editing this diagram.

Aggregation line not added.

All pure virtual methods will be reset to virtual. Continue ?

All virtual methods will be reset to pure virtual. Continue ?

All users have been added to this project's edit list.

An item could not be added due to space constraints.

An off-page connector with output connections cannot be used.

Another user is currently adding this item -- create cannot be performed.

Another user is currently adding this item -- Label cannot be used.

Another user is currently modifying this item -- Cannot be used as a subflow.

Another user is currently modifying this item -- Edit cannot be performed.

Another user is currently modifying this item -- Split cannot be performed.

Another user is editing an item that would be affected -- Operation denied.

Another user is modifying the user list of this project.

Another user is performing an operation requiring exclusive project access.

Attached relationship(s) exist, cannot delete this entity.


B

Bad entry label

Boilerplate not found.

Boilerplate too big to fit on diagram.

Both the Related To and Values & Meanings fields contain information.


C

C struct "X" has no composition defined.

Can't add Trigger "X" to Repository - Name Conflict.

Can't add Trigger "X" to Repository - Name Conflict.

Can't change process # -- Diagrams that would be affected are being edited.

Can't get device context for printer.

Can't get repository Handle.

Can't identify parent

Can't perform global change -- Diagrams that would be affected are being edited.

Can't perform conversion, project is not in version 3.1 format.

Can't perform Nest -- Diagrams that would be affected are being edited.

Cannot add because record already exists.

Cannot add this alias -- It already exists as another entry.

Cannot copy portion of project that contains context diagram.

Cannot delete record because it doesn't exist.

Cannot get record because it doesn't exist.

Cannot open reports file.

Cannot open SQLDIAL.TBL file.

Cannot perform Spawn -- Diagrams that would be affected are being edited.

Class type not specified for X'.

COBOL configuration file "X" cannot be opened. Can't generate COBOL code.

COBOL configuration file "X" contains invalid data. Can't generate COBOL code.

Component must have a name.

Conflict between default VALUE and USAGE INDEX or REDEFINES for item "X". The default VALUE has been ignored.

Conflict between picture and USAGE INDEX for item "X". The picture has been ignored.

Conflict between picture class and the number of decimal places for item "X". The number of decimal places has been ignored.

Connected page does not exist.

Construct "X" not found. Enter new location:    .

Construct exceeds page size.

Could not add a user defined type for the current field.

Couple "X" used in "Y" has the same C name as a module.

Couples "X" and "Y" used in "Z" have the same C name.


D

Database is corrupt. Run Rebuild and try again.

Date constant expected.

DLL "X" not found. Cannot import.

Decomposition hierarchy incompatible with data flow diagrams.

Diagram exceeds maximum page size.

Diagram file 'X' was not found, an empty one will be created.

Diagram label already used in this project -- Enter another label.

DOS file name for program "X" is not unique, file "Y" has been overwritten.

Duplicate "X" clause.

Duplicate couple "X" in call between "Y" and "Z".

Duplicate definition for "X".

Duplicate label encountered, object label not added.

Duplicate parameter "X".


E

Entry could not be found that matches current entry characteristics.

Entry type expected.

Error reading file.

Error reading reports file.

Error reading user-defined object links.  Delete entry and run rebuild.

Error writing reports file.

Export failed -- Could not create export files.


F

Fatal error splitting view(s).

File not found.

Files damaged, must rebuild.

First character of repository name not a letter.

Flow selected is not attached to the parent process of this diagram.

Function must be decomposed directly to processes before a Spawn operation.

Functional decomposition error(s) encountered -- Try analyze.


I

Illegal character -- Used as a delimiter in database.

Import cannot create an invocation.

Import cannot open log file "X".

Import DLL error in "X": #Y Import file format incorrect.

Import DLL error in "X": #Y Internal -- Exit and restart the Visible Analyst.

Import DLL error in "X": #Y Unable to open import file(s).

Import DLL error in "X": #Y Undefined.

Import file not found.

Import object type conflicts with existing object, item not imported.

Import procedure aborted, X records have been imported.

Improper format for count of items.

Initialization failure -- .

Integer constant expected.

Invalid Alias Owner.

Invalid condition.

Invalid construct name.

Invalid construct name, reserved DOS device.

Invalid entry types list.

Invalid file name.

Invalid format value "X".

Invalid label to use in split. -- Label used else where in project.

Invalid Location entry.

Invalid 'order by' value X.

Invalid path specified.

Invalid placement of '|' in Composition of "X".

Invalid project name.

Invalid report name.

Invalid 'select' value X.

Invalid SQL dialect format in SQLDIAL.TBL file -- Reload from master disk.

Invalid storage types list.

Invalid VAW construct file format.

Invalid 'where' expression.

Invocation(s) from Macro "X" cannot be generated; not a recommended type of connection.

Item named "X" altered to name "Y" to meet COBOL rules.

Item named "X" altered to program name "Y" to meet COBOL rules.

Item not decomposed beyond the 01 level: "X".

Item not fully decomposed to data elements: "X".


K

Key already exists.

Key does not exist.


L

Labels must be unique -- Label used elsewhere in project.

Last record in file is not complete.

Loading this construct would exceed diagram limits.

Location(s) exist, cannot delete this entry.

Low memory warning: Approaching limit of diagram complexity. Save work


M

Matrix report is empty.

Maximum number of projects reached, can't create.

Maximum number of levels in decomposition hierarchy has been reached.

Maximum number of symbols for this diagram.

Maximum number of users already logged on!.

Member name is already used with a different class type.

Member X is used more than once.

Missing 'format' value.

Missing 'order by' value.

Missing 'restriction' condition.

Missing select value.

Modify rights to the project directory are required to perform this operation.

More than one returned couple in call between "X" and "Y".

Multiple associator elements on a relationship.

Multiple Data Only Modules specified in an Information Cluster.

Multiple invocations of "X" have different number of parameters.

Multiple invocations of "X" have parameter of different type.

Multiple invocations of "X" have return values of different type.

Multiple Related To items specified.


N

Name exceeds 40 characters.

Name not specified where required.

Name of connected item is not a valid VSC name.

Nested braces in composition of "X".

NetWare shell is not loaded.

No complete clusters exist on this view.

No entities are available for inclusion in cluster.

No entries in repository.

No length specified for item "X". Using Y.

No more entries.

No reports found in reports file.

No space left on drive.

No valid programs in the project "X". Using the entire project.

Not enough memory to execute this function.


O

Object type is not supported by this version of the Visible Analyst.

Only one process is allowed on a context diagram.

Only one project is allowed in the Educational Version.

Only someone logged in as SUPERVISOR can turn off security.


P

Parameters missing.

Parent already has 40 children.

Parent missing. Must restore before editing children.

Problem accessing database files. -- Operation canceled.

Problem accessing security file.

Problem creating directory -- Cannot proceed with operation.

Problem creating project repository -- Cannot proceed with operation.

Problem creating network transaction file -- Cannot proceed with create.

Problem opening treefile -- Cannot proceed with operation.

Problem reading project treefile -- Cannot perform save.

Problem reading project treefile -- Cannot print.

Problem sending message.

Problem with current device.

Problem with transaction log -- Cannot proceed.

Process number already in use.

Process view is empty.

Program "X" has invalid root module.

Project "X" not found. Enter new location:   .

Project already exists.

Project already has maximum number of diagrams.

Project contains maximum number of diagrams, cannot perform function.

Project does not exist.

Project files damaged or not convertible.

Project is currently being created by another user -- Cannot proceed.

Project master file cannot be opened -- may be damaged.

Project not found in masterfile.

Project version (X.Y) not supported.

Project's database files not found.


Q

Query definition error: "X".


R

Rebuild failed. Cannot create data store list.

Rebuild failed. Cannot create work files for project "X".

Record header format is not correct.

Relationship already exists with different cardinality.

Relationship already exists with different set of names.

Report "X" not found.

Report name missing.

Report saver file is empty.

Repository string exceeds the maximum length.

Restriction too long.

Return value from "X" is sometimes ignored.

Root module for C program "X" is not named 'main'.


S

Security cannot be disabled for network version of the Workbench.

Selected SQL dialect is not defined in SQLDIAL.TBL -- reload from master disk.

Some components already exist - conflicting information was not changed.

Storage type expected.

String constant expected.

Subdirectory could not be created.


T

Template files missing -- Reload from master diskette.

Text string is not in the proper format.

The first character of a label must be a letter when rules are enabled.

The item "X" is not valid when combined with the other line parameters you have previously chosen.

The Main Transaction Log could not be accessed.

The maximum number of projects have already been created.

There are more than two description lines.

There are no items defined in this block

There are no items defined in this block.

There are no virtual methods defined for this class.

There are too many lines in entry.

These PERFORM statements are generated from invocation lines.

This class appears on an entity-relationship diagram.

This couple exists on other diagrams, so it may not be changed.

This entry has been deleted.

This file is currently locked by another user.

This is disk X of the backup. Please insert backup disk Y.

This is not a conditional invocation line. -- Reposition start point.

This item cannot be deleted or modified.

This operation would exceed the 600 diagram limit.

This page already contains the maximum of 750 text items per page.

This page already contains the maximum of 500 lines per page .

This page already contains the maximum of 250 symbols per page.

This PERFORM statement is generated from an invocation line.

This project is stored on a local drive to which you do not have access.

Too many flows to fit on diagram. -- Remaining flows ignored.

Too many parameters.

Too many reports.

Tree file already exists in this subdirectory -- Select another path.

Trigger "X" already in repository. Add to Table?.

Type for couple "X" cannot be determined.


U

Unable to access path\file.

Unable to delete directory.

Unbalanced braces in composition of "X".

Unbalanced parentheses.

Unexpected eof.

Unexpected error during VA operation.

Unknown column "X".

Unknown parameter "X".

User file cannot be accessed if security is disabled.

User not logged on.


V

VR Repository Access Error (Error Displays as a Dialog Box)


W

Warning: "X" in composition field has an invalid type for this object.

Warning: "X" in composition field is referenced by another cluster.

Warning: A pure virtual method should not have a definition.  Continue?

Warning: both Related To and Values & Meanings contain information.

Warning: Related to entry "X" does not exist in the repository.

Warning: Relationship "XrY" omitted from schema because it doesn't appear on the included view(s).

Warning: Relationship "XrY" omitted from schema because Entity "Z" doesn't appear on the included view(s).

Warning: This entry type is normally related to a data element.

Warning: This entry type is normally related to a process.

Warning: This entry type is normally related to an element, data structure, data flow, or file.


Y

You do not have rights to this directory.

You do not have rights to update the VAW.INI file.

You have insufficient rights to the directory where the Visible Analyst is installed.

You have not been assigned access rights to this project.

You have not been assigned modify rights to this project.

You may not use arcs and elbows for invocation lines which have couples.

You must have exclusive rights to branch -- Another user is editing a child diagram.

You must have exclusive rights to project to perform this operation.

You must have exclusive rights to project to perform this operation.

You must have rules & repository support to access this project.

You must select an invocation line before pasting unassociated couples.

You must Undo changes to the current line-in-progress to change modes.

Your selection would create more than one top level diagram.


A change is pending for this diagram -- Cannot edit.

Another user has performed a global change that could affect this diagram. You cannot access the diagram until the other user saves his work or aborts the edit.


A class must be labeled before a Nest operation can be performed.

An un-named class cannot be decomposed.


A couple may only be changed into another couple type.

Once a couple line type is created, the Change Type option will limit its transformation to other couple line types. For instance, a generic couple can be changed to a data couple however, the generic couple cannot be changed to a loop line.


A diagram is being inserted into the tree -- This branch cannot be altered.

Another user is inserting a diagram into the tree that could affect the diagram you have selected. The diagram cannot be edited. To determine the USER ID of the person inserting the diagram, select the Current Activity option from the File menu and find the users with an activity of is creating new diagram. The person in question will be one of these users and you may contact him/her by utilizing the message facility (press the F5 key).


A non-couple cannot be changed to a couple.

The Change Type option in the Change Type dialog box cannot be used to transform an invocation line or loop line type into a couple.


A non-loop may not be changed into a loop.

The Change Type option on the Change Type dialog box cannot be used to transform an invocation line or a couple into a loop line.


A process must be added to this context diagram.

A process must be added and named before the diagram is saved when a context diagram was requested.


A process must be labeled before a nested decomposition can be performed.

An unnamed process cannot be decomposed.


A Program can only have one item as the root module.

The composition field of a program indicates the top level module of that program. Only one module may be specified.


A relationship can be labeled only when two NAMED entities are attached.

A relationship only has meaning when attached to two entities. It must join two entities before a relationship can be labeled and added to the repository.


A supertype/inheritance relationship already exists between this pair of objects.

Only one supertype or inheritance relationship can be drawn between a pair of entities or classes.


A supertype/inheritance relationship cannot be recursive.

A supertype or inheritance relationship cannot be drawn such that the start and endpoints are the same object.


A supertype relationship cannot be used with a non-fundamental entity.

A supertype relationship cannot be drawn if the child entity is either an associative or attributive entity. These entity types imply special relationships to their parents which are in conflict with supertype relationships. Either draw a different type of relationship or change the entity type to fundamental.


A tree file for project "X" is damaged or missing.

When copying a portion of a project, the treefile could not be found or was damaged. Restore the project.


A user-defined object cannot have the same name as a VAW entry type.

When creating a user-defined object, the name of the object cannot be the same as any of the built-in VAW types. For example, you cannot create an object named Process.


Access denied -- another user is editing this diagram.

A diagram can be edited by only one user at a time. The selected diagram is already in use.


Aggregation line not added.

A construct that was originally created from a class diagram can be loaded into a entity relationship diagram. However, aggregation relationships are not supported on ERDs so those relationship types will be ignored.


All pure virtual methods will be reset to virtual. Continue ?
All pure virtual methods will be reset to virtual. Continue ?.

If you want to change an abstract class to a concrete class, the class definition cannot contain pure virtual methods because a concrete class can be instatiated. The VAW will reset pure virtual methods to virtual in this case.


All virtual methods will be reset to pure virtual. Continue ?

If you want to change a concrete class to an abstract class, the VAW will reset virtual methods to pure virtual.


All users have been added to this project's edit list.

All users currently defined to NetWare have been assigned to this project. There are none left to add.


An item could not be added due to space constraints.

When loading a construct, the maximum number of objects was reached before the entire construct could be loaded.


An off-page connector with output connections cannot be used.

An off-page connector with input connections (invocation lines drawn from a module symbol to the off-page connector) is acting as a reference to a module on another diagram. The Page function can operate on this type of page connector. An off-page connector with output connections (an invocation line drawn from the off-page connector to another symbol) cannot be the object of a Page function.


Another user is currently adding this item -- create cannot be performed.

Someone has created the specified item, but it has not been saved. Press the Details button for more information.


Another user is currently adding this item -- Label cannot be used.

Another user is adding this item to the repository but it has not been saved. Try again later or press the Details button for more information.


Another user is currently modifying this item -- Cannot be used as a
Another user is currently modifying this item -- Cannot be used as a subflow.

If another user is modifying a data flow's repository entry, it cannot be used as a subflow.


Another user is currently modifying this item -- Edit cannot be performed.

Only one user can edit a repository entry at one time.


Another user is currently modifying this item -- Split cannot be performed.

Another user is modifying the repository entry for this data flow. The Split operation cannot be performed.


Another user is editing an item that would be affected -- Operation denied.

If a name change is attempted on a repository item, and another user is editing a component item, the operation will be denied.


Another user is modifying the user list of this project.

Only one user at a time can change the list of users that can access a project.


Another user is performing an operation requiring exclusive project
Another user is performing an operation requiring exclusive project access.

This project cannot be accessed until the user currently performing an operation requiring exclusive rights is complete. These operations include all the operations on the Utilities menu such as Backup, Restore, Copy Portion, etc.


Attached relationship(s) exist, cannot delete this entity.

An entity cannot be deleted inside the repository if relationships are attached to that entity in its repository entry. All relationships attached to this entity must be deleted before it can be deleted.


Bad entry label

Label does not begin with an alphabetic character.


Boilerplate not found.

The boilerplate you requested for this diagram cannot be found.


Boilerplate too big to fit on diagram.

The current boilerplate is larger than the selected diagram size. Either make the diagram drawing area larger or change the boilerplate.


Both the Related To and Values & Meanings fields contain information.

Only one of these fields may contain a value. If you declare that this item is related to another existing item, the values and meanings information should be specified in the repository entry for that item.


C struct "X" has no composition defined.

A data structure exists in the repository that has nothing in its composition field.


Can't add Check condition "X" to Repository -- Name Conflict
Can't add Check condition "X" to Repository - Name Conflict.

The name of the Check condition you are trying to add to the repository is the same as another object already in the repository. You must select another name to add it.


Can't add Trigger "X" to Repository - Name Conflict
Can't add Trigger "X" to Repository - Name Conflict.

The name of the trigger you are trying to add to the repository is the same as another object already in the repository. You must select another name to add it.


Can't change process # -- Diagrams that would be affected are being
Can't change process # -- Diagrams that would be affected are being edited.

A process number change effects all child diagrams in the same branch of the tree. Another user is editing one of these diagrams so the operation is denied.


Can't get device context for printer.

Windows was unable to access the selected printer. Verify the printer settings.


Can't get repository handle.

The Workbench could not find the repository for this project. Make sure that your files have not been moved or deleted.


Can't identify parent
Can't identify parent.

You asked the Workbench to draw lines connecting symbols in a block on an FDD. The Workbench could not identify which symbol should be the parent, probably because the symbols are all in the same horizontal row.


Can't perform global change -- Diagrams that would be affected are being
Can't perform global change -- Diagrams that would be affected are being edited.

Another user is currently editing a diagram that would be affected by a global change so the operation is denied.


Can't perform conversion, project is not in version 3.1 format.

In order to be converted to the format of the current version, a project must first be in version 3.1 (or later) format. If you have a version of the Visible Analyst Workbench older than version 3.1, please call Visible Systems Corporation so that we can assist you in this conversion.


Can't perform Nest -- Diagrams that would be affected are being edited.
Can't perform Nest -- Diagrams that would be affected are being edited

Another person is editing the diagram or a child of the diagram whose name was selected as the object of a Nest operation. Use the Current Activity facility on the File menu to determine the USER IDs of these people and send an appropriate message to them using the messaging facility. Press the F5 key to access the message facility.


Cannot add because record already exists.

A user cannot be added to the list of valid users because the name is already used.


Cannot add this alias -- It already exists as another entry.

The specified alias already exists as another entry type. All items in the repository must be defined with unique labels.


Cannot copy portion of project that contains context diagram.

A context diagram cannot be copied into an existing project. However, the image of the context diagram can be copied into another project by using the Construct function on the Diagram menu. The construct should be created from the existing context diagram and loaded into the copy-to project.

The loading of the construct into the copy-to project will not migrate the data repository information maintained for the objects appearing on the diagram but the information for these objects will be migrated if they are referenced by other diagrams which are included in the Copy Portion operation.

To determine whether the information was migrated, use the Define option on the Repository menu and select each object to view its data repository definition.


Cannot delete record because it doesn't exist.

This user has not been added to security list, so his/her USER ID cannot be deleted.


Cannot get record because it doesn't exist.

There is no security record for the user you specified.


Cannot open reports file.

The custom reports definition file REPORTS.TBL could not be opened. It has been deleted or is otherwise unavailable. Since it is necessary to the operation you just requested, you should copy it from your set of master diskettes.


Cannot open SQLDIAL.TBL file.

The file SQLDIAL.TBL contains information on all SQL dialects supported by the Workbench. It has been deleted or is otherwise unavailable. Since it is necessary to the operation you just requested, you should copy it from your set of master diskettes.


Cannot perform Spawn -- Diagrams that would be affected are being
Cannot perform Spawn -- Diagrams that would be affected are being edited.

The Spawn function effects all diagrams in same branch of the DFD tree, and one or more users are editing some of these diagrams. Use the Current Activity facility on the File menu to determine the USER IDs of these people and send an appropriate message to them using the messaging facility. Press the F5 key to access the message facility.


Class type not specified for X'.

When defining attributes for a class, the type is required.


COBOL configuration file "X" cannot be opened. Can't generate COBOL
COBOL configuration file "X" cannot be opened. Can't generate COBOL code.

The file COBOLTYP.TBL contains information on how COBOL code should be generated. It has been deleted or is otherwise unavailable. Since it is necessary to the operation you just requested, you should copy it from your set of master diskettes.


COBOL configuration file "X" contains invalid data. Can't generate COBOL
COBOL configuration file "X" contains invalid data. Can't generate COBOL code.

The file COBOLTYP.TBL contains information on how COBOL code should be generated. It has been improperly edited or otherwise corrupted. Since it is necessary to the operation you just requested, you should fix the editing improprieties (if you are certain how to do so) or copy it from your set of master diskettes.


Component must have a name.

When defining components using the Add Components dialog, a name must be given for each component. The name will be used to reference the component in the repository and is thus required.


Conflict between default VALUE and USAGE INDEX or REDEFINES for item "X".
Conflict between default VALUE and USAGE INDEX or REDEFINES for item "X". The default VALUE has been ignored.

The file COBOLTYP.TBL contains information on how COBOL code should be generated. There is a conflict between specifications in this file and the information you have specified in the repository, or an internal inconsistency in specifications in this repository entry. The code generator will continue to generate code, but it will ignore what you specified for the default value for this item.


Conflict between picture and USAGE INDEX for item "X".
Conflict between picture and USAGE INDEX for item "X". The picture has been ignored.

The file COBOLTYP.TBL contains information on how COBOL code should be generated. There is a conflict between specifications in this file and the information you have specified in the repository, or an internal inconsistency in specifications in this repository entry. The code generator will continue to generate code, but it will ignore what you specified for the picture for this item.


Conflict between picture class and the number of decimal places for item "X".
Conflict between picture class and the number of decimal places for item "X". The number of decimal places has been ignored.

The file COBOLTYP.TBL contains information on how COBOL code should be generated. There is a conflict between specifications in this file and the information you have specified in the repository, or an internal inconsistency in specifications in this repository entry. The code generator will continue to generate code, but it will ignore what you specified for the number of decimal places for this item.


Connected page does not exist.

This diagram has been connected to another diagram with the Page function. The connected diagram has been deleted.


Construct "X" not found. Enter new location:    .

The construct file for the construct you selected has been deleted or is otherwise unavailable. If the file has been moved to another disk location, enter its path. If the file no longer exists, you should eliminate the dangling construct name and prevent recurrence of this error message. To do this, press Cancel. Then press the Delete button in the Construct dialog box to eliminate the construct name which generated this error.


Construct exceeds page size.

The current construct is of easel size and cannot be loaded into the current diagram, which is standard size. Either make the diagram drawing area larger or use a different construct.


Could not add a user defined type for the current field.

.


Couple "X" used in "Y" has the same C name as a module.

The naming rules and name length requirements for the Workbench are different for those in C. When generating shell code for C, repository item names must be transformed into valid C names. It is possible for two differently named items in the Workbench to end up with the same C name. This would cause you problems if you try to compile this generated code. You should change one of the names so that the generated code name will be different from that for the other item.


Couples "X" and "Y" used in "Z" have the same C name.

The naming rules and name length requirements for the Workbench are different for those in C. When generating shell code for C, repository item names must be transformed into valid C names. It is possible for two differently named items in the Workbench to end up with the same C name. This would cause you problems if you try to compile this generated code. You should change one of the names so that the generated code name will be different from that for the other item.


Database is corrupt. Run Rebuild and try again.

Something happened to the project database Run Rebuild from the Utilities menu to restore it to normal functioning.


Date constant expected.

A date constant is required in a 'where' clause restriction.


DLL "X" not found. Cannot import.

The dynamic link library (DLL) program file specified is missing or not in the VA directory.


Decomposition hierarchy incompatible with data flow diagrams.

Changes have been made to a set of data flow diagrams spawned from an FDD function that are inconsistent with the set of processes descending from that function on the FDD. The Spawn Verify function cannot reconcile them. You must manually change one set of diagrams to match the other. To avoid this error in the future, changes to the hierarchy of functions and processes should be made to the FDD. Then you can let the Spawn function carry the changes to the DFDs rather than editing them both independently.


Diagram exceeds maximum page size.

The Workbench could not automatically draw an editable view because all of the items you specified to include in the view could not be included without having to overlay symbols. You have several options:

You can print the view to see what it looks like and make up your mind what to do later.

You can return to the selection process and select fewer items to include in the view.

You can decrease the size of the symbols in the symbol template, which might sufficiently ease the crowding of symbols to make it possible to draw an editable diagram.

You can create clusters including some of the entities on this view and create an unstructured cluster diagram.

You can reduce the point size of the fonts used for the text used to label lines and symbols before generating the view. This will cause the Workbench to scale the size of the symbols and lines down to match the text and squeeze more information onto the view. The more important of the two is the text used to label the relationships because it will decrease the space between the entities.

Your best option is probably to reduce the number of entities in the view, for a view of the current complexity will probably be difficult to comprehend even if you could create an editable diagram.


Diagram label already used in this project -- Enter another label.

Each diagram in a project must have a unique name.


Diagram file 'X' was not found, an empty one will be created.

Each diagram in a project must have a parameter file which describes the diagram's contents and appearance. This diagram file is not present, probably because it was deleted at the DOS level. An empty parameter file will be created to maintain treefile consistency. If you have a backup of the original file, you can copy it over the empty one created by the Workbench and the diagram will be restored. You should then run Rebuild again to restore diagram's links to the project's repository. No repository descriptive information is lost.


DOS file name for program "X" is not unique, file "Y" has been overwritten.

During shell code generation, the output file created overwrote an existing file.


Duplicate "X" clause.

The indicated clause is duplicates in the custom report specification.


Duplicate couple "X" in call between "Y" and "Z".

A couple appears twice on an invocation line between modules "Y" and "Z". This would cause a duplicated parameter in generated C code. Note that it is possible that this couple appears along the invocation and is also listed in the composition of an ITR that is attached to the invocation. In this case, its duplication would not be obvious from looking at the diagram.


Duplicate definition for "X".

When defining methods for a class, a method name can be used more than once, but each instance must have a different set of arguments to make it unique.


Duplicate label encountered, object label not added.

During a construct load or tree copy operation, any label which could cause two different entry types to share the same name or create a second instance of an object limited to a single appearance on a diagram is ignored. The text of the symbols defined with duplicate labels will be removed resulting in diagrams containing unnamed symbols. An analysis of the project can be employed to identify unlabeled symbols.


Duplicate parameter "X".

There is a duplicate parameter in the 'params' clause of a custom report specification.


Entry could not be found that matches current entry characteristics.

When searching for an item in the repository, an item with the selected entry characteristics could not be found.


Entry type expected.

An entry type is required in the selected report query.


Error reading file.

There was a system error reading a requested file. The current task cannot proceed.


Error reading reports file.

There was a system error reading the saved reports file. The requested report cannot proceed.


Error reading user-defined object links.  Delete entry and run rebuild.

The structure containing links to user-defined objects has been damaged. You must delete this entry and re-create the linkage. This may happen has a result of a power loss during a repository update.


Error writing reports file.

There was a system error writing the saved reports file. The requested report cannot be saved.


Export failed -- Could not create export files.

The files necessary to store exported data could not be created. It could be that there is not enough disk space, that you do not have rights to the destination directory or some system failure. You must rectify the situation before the export can be done.


Fatal error splitting view(s).

A global view could not be split into pages to print. There is probably insufficient disk space.


File not found.

The file specified for import could not be found in the specified directory.


Files damaged, must rebuild.

The repository for the current project has been corrupted. To correct this condition, execute the project Rebuild utility. If the problem persists, contact Visible Systems.


First character of repository name not a letter.

All repository entries must start with a letter.


Flow selected is not attached to the parent process of this diagram.

Only a net input or output flow can be split. A flow attached to a process specified as the target of a Nest (decompose) operation is considered a net input/output flow.


Function must be decomposed directly to processes before a Spawn
Function must be decomposed directly to processes before a Spawn operation.

Only a function all of whose descendants on the FDD are processes can be spawned. If some descendants are subsidiary functions, the Spawn function cannot proceed.


Functional decomposition error(s) encountered -- Try analyze.

A Spawn Verify operation could not be performed because the structure of the functional decomposition diagram does not match the data flow diagram set. Run the Analyze function to determine the cause.


Illegal character -- Used as a delimiter in database.

The label of an entry type such as a data flow, data store or couple, which can appear in the composition field of another data repository entry, may contain up to forty characters. Each can consist of any upper/lower case letter, numbers, spaces, periods, underlines and hyphens. The first character must always be a letter. All other characters are considered as delimiter characters.


Import cannot create an invocation.

The Import function cannot create an invocation described in the import file. This could be because the source and/or destination module names were not present or because the module names were present in the import file but they couldn't be found in the repository and the Workbench couldn't create them (perhaps they were of incompatible types or violated some naming uniqueness rule).


Import cannot open log file "X".

The listed file can not be opened for reading and writing.


Import DLL error in "X": #Y Import file format incorect.
Import DLL error in "X": #Y Import file format incorrect.

The import file specified does not conform to the format required. See specifications for import files from other systems and make sure that the file was created correctly.


Import DLL error in "X": #Y Internal -- Exit and restart the Visible Analyst.

The Import DLL (dynamic link library) failed and its state is invalid. You may have to close and restart Microsoft Windows in order to run the import again. Please contact Visible Systems.


Import DLL error in "X": #Y Unable to open import file(s).

One or more of the import files was not found or cannot be opened.


Import DLL error in "X": #Y Undefined -- Contact Visible Systems.
Import DLL error in "X": #Y Undefined.

An internal error has occurred. Please contact Visible Systems.


Import file not found.

The VSC format import file was not found.


Import object type conflicts with existing object, item not imported.

The object in the import file has a type that cannot coexist with an object already in the repository of a different type.


Import procedure aborted, X records have have been imported.
Import procedure aborted, X records have been imported.

If Import is canceled after the actual import has begun, the number of records imported at the time of the cancellation is displayed.


Improper format for count of items.

In one of the five string sections of a VSC import file, the line that should contain a record count does is not formatted properly. Hint: if one of the counts is wrong, this error could occur when processing the next section.


Initialization failure -- Contact Visible Systems.
Initialization failure.

The network version of the Workbench was not able to access the network. If the network shell is loaded and you are logged on, contact Visible Systems.


Integer constant expected.

An integer constant is required in a 'where' clause restriction.


Invalid Alias Owner.

The alias owner information for an alias record is not valid or compatible with the project in use.


Invalid condition.

There is an invalid restriction condition in a custom report 'where' clause.


Invalid construct name.

The name you specified for a construct contains illegal characters. Please correct and reenter.


Invalid construct name, reserved DOS device.

The entered construct name is a reserved DOS device name.


Invalid entry types list.

There is an invalid entry types list in a custom report 'where' clause.


Invalid file name.

Please specify only the eight character DOS file name.


Invalid format value "X".

There format value indicated in a custom report 'format' clause is invalid.


Invalid label to use in split. -- Label used else where in project.

Data flow labels can be the same as data store labels, but they must be different from process and external entity labels.


Invalid Location entry.

The entry you made in a Location field does not correspond to a repository item. Please enter a correct value or use the Search function to locate it and enter it that way.


Invalid 'order by' value X.

The value you entered in a custom report 'order by' field is not a valid repository entry label or entry type. Please enter a correct value.


Invalid path specified.

The path specified could not be created. Correct and try again.


Invalid placement of '|' in Composition of "X".

The logical OR operator '|' is not placed in a syntactically correct position in the field. Correct and try again.


Invalid project name.

The project name you entered contains invalid characters. Please enter a correct value.


Invalid report name.

The report name you entered contains invalid characters. Please enter a correct value.


Invalid 'select' value X.

The value you entered in a custom report 'select' field is not "*", "detail" or "summary". Please enter a correct value.


Invalid SQL dialect format in SQLDIAL.TBL file -- Reload from master disk.

The format of information in the file SQLDIAL.TBL is incorrect. Perhaps an attempt to customize the file was done incorrectly. Inspect the file customizations for correctness or reload the original file from the master diskettes.


Invalid storage types list.

There is an invalid storage types list in a custom report 'where' clause.


Invalid VAW construct file format.

The format of the file containing the construct you requested is invalid. Please restore a correct file from a backup or delete the construct and recreate it.


Invalid 'where' expression.

The restriction entered in the 'where' clause of a custom report does not evaluate to valid restriction expression. Please consult the manual and correct.


Invocation(s) from Macro "X" cannot be generated; not a recommended
Invocation(s) from Macro "X" cannot be generated; not a recommended type of connection.

A Macro should not invoke another module. Change it to a normal Module.


Item named "X" altered to name "Y" to meet COBOL rules.

The naming rules for the Workbench and COBOL are different. When generating COBOL shell code, the names of some repository objects may be transformed to conform to COBOL specifications.


Item named "X" altered to program name "Y" to meet COBOL rules.

The naming rules for the Workbench and COBOL are different. When generating COBOL shell code, the names of some repository objects may be transformed to conform to COBOL specifications.


Item not decomposed beyond the 01 level: "X".

A non-element repository item has been named but has not been decomposed at all. A correct COBOL data declaration cannot be generated.


Item not fully decomposed to data elements: "X".

A non-element repository item has not been fully decomposed to data elements. A correct COBOL data declaration cannot be generated.


Key already exists.

You attempted to save a new repository item with the same name as one that is already in the repository of your project.


Key does not exist.

The label you entered in the Define dialog box does not exist in the repository. In the educational version of the VAW, items cannot be created directly. They must be created on a diagram or in the composition field of another object, such as an entity or data store.


Labels must be unique -- Label used elsewhere in project.

If you are labeling a process, all names must be unique. If labeling a data flow, data store, or external entity, the name of one type cannot be the same as another type. However, files and data flows can have the same name.


Last record in file is not complete.

The VSC import file ended in the middle of a record.


Loading this construct would exceed diagram limits.

A construct could not added to a diagram due to size constraints.


Location(s) exist, cannot delete this entry.

An item cannot be deleted from the data repository if it exists on a diagram or as an entry in the composition field of another data repository entry. To delete this item, it must be deleted from any diagram it appears on and its label must be removed from the composition field of entries which reference it.


Low memory warning: Approaching limit of diagram complexity. Save work

The amount of space allocated for this diagram is almost depleted. To avoid loss of work, execute the Save function. We suggest you either partition the diagram into multiple diagrams or add no more objects to it.


Matrix report is empty.

There were no repository objects that met the requirements you specified for a matrix report.


Maximum number of projects reached, can't create.

The completion of a New Project operation would have exceeded the maximum project count restriction. The following lines describe the maximum project count for each configuration:

Educational -- 1

Professional -- limited to the available disk space.

To determine your product's configuration, open the Help menu and select the About Visible Analyst function.


Maximum number of levels in decomposition hierarchy has been reached.

You have already nested to the maximum level allowed by the Workbench (twenty levels). The current Nest operation would exceed that maximum and is not allowed.


Maximum number of symbols for this diagram.

You have already reached the maximum number of symbols on a diagram allowed by the Workbench (two hundred and fifty). The current operation would exceed that maximum and is not allowed.


Maximum number of users already logged on!.

The maximum number of users (or nodes) allowed for the tool you purchased are already logged on. You cannot log on until one of the others logs off.


Member name is already used with a different class type.

When defining role names for a relationship, the name selected for the role already appears as a member of the opposite class but with a different class type than that of the current class. Because member names must be unique within a class, you must choose a different name for the role. For example, if you had a class named Window with a relationship to Item, and you defined the role for Window as pWindow, there must be a member called pWindow of type Window in the member list of Item.


Member X is used more than once.
Member 'X' is used more than once.

Member names must be unique within a class.


Missing 'format' value.

There is no value entered in a custom report 'format' field. It should be multiple or single. Please enter a correct value.


Missing 'order by' value.

There is no value entered in a custom report 'order by' field. It should be a valid repository entry label or entry type. Please enter a correct value.


Missing 'restriction' condition.

There is no restriction entered in the 'where' clause of a custom report. Please consult the manual and correct.


Missing select value.

There is no value entered in a custom report 'select' field. It should be k, detail or summary. Please enter a correct value.


Modify rights to the project directory are required to perform this
Modify rights to the project directory are required to perform this operation.

The creator of this project or a supervisor has given you view-only rights. One of those people must upgrade your rights before you can make any changes to this project.


More than one returned couple in call between "X" and "Y".

More than one couple appears on an invocation line between modules "X" and "Y" in the return direction. This would cause a function with more than one return value in generated C code and is not allowed.


Multiple associator elements on a relationship.

A relationship may have only one associator element.


Multiple Data Only Modules specified in an Information Cluster.

One of the standard modules you specified for the information cluster is in fact a data only module. An information cluster can have only one data only module.


Multiple invocations of "X" have different number of parameters.

You have invoked module "X" in different places on your structure chart with different numbers of couples along the invocation line. The code generator cannot produce proper C code in this situation.


Multiple invocations of "X" have parameter of different type.

You have invoked module "X" in different places on your structure chart with couples corresponding to repository items of different types. The code generator cannot produce proper C code in this situation. Note that it is possible that these couples could exist as components of ITRs attached to the invocations. In this case, the variations would not be obvious from looking at the diagrams.


Multiple invocations of "X" have return values of different type.

You have invoked module "X" in different places on your structure chart with one couple appearing on invocation lines to module "X" in the return direction corresponding to repository items of different types in different instances. The code generator cannot produce proper C code in this situation.


Multiple Related To items specified.

More than one Related To items were specified in a field in an import file.


Name exceeds 40 characters.

The name you entered exceeds the Workbench maximum of forty characters.


Name not specified where required.

You have not entered the name of a repository item where one is required.


Name of connected item is not a valid VSC name.

A name you entered contains invalid characters. Please reenter.


Nested braces in composition of "X".

Curly braces cannot be nested in a composition field to show array structure.


NetWare shell is not loaded.

You have attempted to run the LAN version of the Workbench when both of the NetWare shell programs IPX.COM and NETx.COM are not memory resident. Load them into memory and then restart the Workbench.


No complete clusters exist on this view.

A cluster view will replace a group of entities with a cluster on a cluster diagram only when all of the entities composing the cluster appear on the current view. Partial clusters will be ignored. Either none of the entities appearing on the current view are members of clusters or there is no cluster for which all of the composing entities exist on this view. In both cases, the cluster view will be the same as the existing view.


No entities are available for inclusion in cluster.

Either there are no entities in the project or all of the entities are currently members of clusters and the free entity pool is empty. An entity can be a member of no more than one cluster.


No entries in repository.

A view can be created by the selection process only when there are already entities and relationships in the repository from which to select. You must either create your view manually, by adding entities and relationships to blank diagrams, or you must enter the repository using the Define function from the Repository menu and create entity entries; then you can add them to a diagram and draw relationships between them.


No length specified for item "X". Using Y.

Item "X" has no length specified in its repository entry. Shell code will be generated using the default value Y.


No more entries.

While searching for the next item in the repository, the end of list has been reached.


No reports found in reports file.

The report saver file is empty.


No space left on drive.

The target drive is full or there is not enough space to copy all of the files.


No valid programs in the project "X". Using the entire project.

There is no Program item in your project's repository referring to a module for which to generate shell code. The code generator will assume that you want a code for a program corresponding to your entire project structure chart.


Not enough memory to execute this function.

While printing a report, Windows could not allocate the memory space required to process the report.


Object type is not supported by this version of the Visible Analyst.

The item you are attempting to open is of a type that is not supported by this version of the Visible Analyst. For example, if your tool set does not support object modeling, you cannot access class and member objects that were created by other VAW toolsets. Contact Visible Systems to upgrade your product configuration.


Only one process is allowed on a context diagram.

Because the context diagram defines the scope of the project, only one process is allowed. It is numbered as process 0.


Only one project is allowed in the Educational Version.

The educational configuration of the product limits the user to editing one project at a time. However, the user may maintain other projects on backup diskettes created by the Workbench Backup utility. When these projects are needed, the user should Backup and delete the current project then Restore the required project.


Only someone logged in as SUPERVISOR can turn off security.

To disable security for the single user version of the Workbench, the user must be named SUPERVISOR.


Parameters missing.

There is one or more missing parameters in the 'params' clause of a custom report specification.


Parent already has 40 children.

Each diagram in a project can have a maximum of forty diagrams on the level immediately below it. The New Diagram, Nest or Page operation cannot continue.


Parent missing. Must restore before editing children.

The parent diagram of the selected child cannot be located in the directory containing the project. A DOS delete or rename command could have caused this condition. To correct this condition, Restore the project's data files from the backup diskette(s) generated by a Workbench Backup operation.


Problem accessing database files. -- Operation canceled.

An unexpected error status was returned from the record manager. To correct this condition, execute the project Rebuild function. If the problem persists, contact Visible Systems.


Problem accessing security file.

The SECURITY.MAS file is missing or damaged. Contact Visible Systems.


Problem creating directory -- Cannot proceed with operation.

When creating a new project, there was a problem creating the needed subdirectory. Either you have insufficient rights to perform the operation, or there was a problem with the drive.


Problem creating project repository -- Cannot proceed with operation.

When creating a new project, there was a problem creating the needed files. Either you have insufficient rights to perform the operation, there is insufficient disk space or there was a problem with the drive.


Problem creating network transaction file -- Cannot proceed with create.

Critical error, contact Visible Systems.


Problem opening treefile -- Cannot proceed with operation.

Critical error, contact Visible Systems.


Problem reading project treefile -- Cannot perform save.

Critical error, contact Visible Systems.


Problem reading project treefile -- Cannot print.

Critical error, contact Visible Systems.


Problem sending message.

A message could not be sent to the selected user. It could be that the user is not logged in on the network. Otherwise, try reloading the network shell.


Problem with current device.

Windows had a problem accessing the output device you have specified.


Problem with transaction log -- Cannot proceed.

Critical error, contact Visible Systems.


Process number already in use.

The specified process number is already used. A process number must be of the form 'Parent-number + . + Child-number' where child-number is a unique number between one and one hundred.


Process view is empty.

You have attempted to create a process view and indicated a process that does not use data elements listed in the composition field of any existing entity. There must be data flows either entering or leaving the process that are composed directly or indirectly of data elements which one or more entities list in their composition fields.


Program "X" has invalid root module.

The specified Program repository item does not have a module listed in its composition field.


Project "X" not found. Enter new location:   .

This project could not be found in the directory path where other projects reside. Perhaps it is on another drive or in another directory, or perhaps it is on a server or a local drive.


Project already exists.

The project specified for creation already exists.


Project already has maximum number of diagrams.

The diagram count for the current project involved in a New Diagram operation or the Copy Project or Copy Portion operation will exceed the maximum allowable diagram count if the operation were to complete. The following lines describe the maximum diagram count for the each configuration:

Educational -- 10

Professional -- 600

To determine your product's configuration, open the Help menu and select the About Visible Analyst function.


Project contains maximum number of diagrams, cannot perform function.

This project contains the maximum of 600 diagrams for this diagram type. No new diagrams can be added.


Project does not exist.

The project root that was entered could not be found in the project master list. Try restoring the project from a set of backup diskettes.


Project files damaged or not convertable.
Project files damaged or not convertible.

A project created with an earlier version of the Workbench is damaged or not complete and cannot be converted to the current release.


Project is currently being created by another user -- Cannot proceed.

The project specified is being created by another user. Either select another project root name or wait until the other user saves his or her work.


Project master file cannot be opened -- may be damaged.

There was a problem accessing the project master file. Contact Visible Systems.


Project not found in masterfile.

The selected project could not be found in the list of projects.


Project version (X.Y) not supported.

This project was created with a prior version of the Workbench. It must be converted to version 5.0 before being used. To convert a 3.1 or later project to version 5.0, execute the Rebuild utility. However, if the project was created by a version prior to 3.1 then contact Visible Systems. We can convert it for you.


Project's database files not found.

The database files for this project could not be found in the directory where the project resides. Either the files have been deleted or moved with DOS functions. They need to be restored to the proper directory before the Workbench can proceed. You also have the option of restoring the most recently backed up version of the project.


Query definition error: "X".

The specified error occurred when you defined a custom report query. Please correct and reenter.


Rebuild failed. Cannot create data store list.

Rebuild could not access or update the temporary project.


Rebuild failed. Cannot create work files for project "X".

Your system may be low on memory or disk space.


Record header format is not correct.

The header for an import record is not properly formed.


Relationship already exists with different cardinality.

A relationship actually consists of the relationship itself and the two entities to which it is attached. An entity/relationship combination can appear on multiple views, but only once per view. However, each occurrence must specify the same cardinality. You are attempting to specify a cardinality for a relationship different from how it appears on another view.


Relationship already exists with different set of names.

A relationship actually consists of the relationship itself and the two entities to which it is attached. An entity/relationship combination can appear on multiple views, but only once per view. However, on each occurrence, the relationship must have the same names in both directions. You are attempting to specify a relationship with mismatched names in the opposing directions of the relationship.


Report "X" not found.

The report you requested from the report saver file could not be found. The report names contained in the file are listed in the dialog box. You can pick one from the list.


Report name missing.

The report name is missing in the 'report' clause of a custom report specification.


Report saver file is empty.

No report format files have been created. To create a saved report, define a report in the Reports dialog box and press the Save Report button. In the subsequent dialog box, give the report a name and press OK.


Repository string exceeds the maximum length.

One of the strings in a VSC import file exceeds sixty characters in overall length.


Restriction too long.

The restriction entered in the custom report definition 'where' clause is too long.


Return value from "X" is sometimes ignored.

Some invocations of module "X" do not have a return couple and some do. This should be done consistently.


Root module for C program "X" is not named 'main'.

The module named in the repository Program item for which shell code is being generated needs to be named main for C programs.


Security cannot be disabled for network version of the Workbench.

In order for the Workbench to work properly on a network, security must always be turned on.


Selected SQL dialect is not defined in SQLDIAL.TBL -- reload from master
Selected SQL dialect is not defined in SQLDIAL.TBL -- reload from master disk.

The information for the SQL dialect you have selected is not in the file SQLDIAL.TBL. You should reload the file from the master diskettes.


Some components already exist - conflicting information was not changed.
Some components already exist - conflicting information was not changed

When defining components using the Add Components dialog, an item was defined that already existed in the repository but with different characteristics. The original characteristics were not modified.


Storage type expected.

A storage type is required in a custom report specification.


String constant expected.

A string constant is required in a 'where' clause restriction.


Subdirectory could not be created.

A default subdirectory could not be created for your new project either because your disk is full, there are no more available directory entries (a very rare occurrence) or because you do not have rights to create subdirectories from the current directory. Check your available disk space or check with your network administrator.


Template files missing -- Reload from master diskette.

One of the symbol template files (TEMPLATE, TEMPLATE.SC, TEMPLATE.ER, TEMPLATE.US or TEMPLATE.FD) is missing. Reload from master diskette.


Text string is not in the proper format.

All strings in the import file must be enclosed in quotes.


The first character of a label must be a letter when rules are enabled.

All entries in the project's repository must begin with a letter when rules are enabled.


The item "X" is not valid when combined with the other line parameters you have previously.
The item "X" is not valid when combined with the other line parameters you have previously chosen.

Not all combination of line elements are valid. If you select an invalid combination, you cannot continue. Either reset to a valid setting or cancel the operation.


The Main Transaction Log could not be accessed.

The Workbench could not open the Main Transaction Log for some reason. Please call Visible Systems Corporation so that we can assist you.


The maximum number of projects have already been created.

In the educational version of the VAW, only one project can be created. If you want to create another project, you must delete the current project before continuing.


There are no items defined in this block

When defining an area for a block selection or move, or a construct, there were no items completely within the displayed box.


There are no virtual methods defined for this class.

Only classes with virtual or pure virtual methods can be marked as abstract. The VAW will automatically mark classes with pure virtual methods as abstract.


There are too many lines in entry.

There are more than 500 lines for a repository field in an import file. Condense the data for the field into fewer lines.


There are more than two description lines.

An import file has more than two lines of description information.


There are no items defined in this block.

No diagram object is completely within the block you have designated. Recreate the block making sure it completely encloses the item(s) you desire to select.


These PERFORM statements are generated from invocation lines.

You have specified that module description fields are to be interpreted as COBOL code and placed into your generated shell code. Therefore, the PERFORM statements that would otherwise be generated from module invocations appearing on structure chart diagrams will not be used as generated code. Rather, they will be placed in the code as comments for your reference, to compare against the code stored in the module description field.


This class appears on an entity-relationship diagram.

If a class appears on an entity-relationship diagram, the persistent indicator cannot be turned off. This is because an entity or table outlasts the execution of a program.


This couple exists on other diagrams, so it may not be changed.

Couples of different types cannot have the same name. You have tried to locally change a couple to a different type when the original couple has locations on other diagrams. Either choose a new name for the couple before attempting to change the type or make the type change global, throughout your project.


This entry has been deleted.

The item selected has been deleted by another user since the window was displayed. Select another entry.


This file is currently locked by another user.

The file specified for import or export is being accessed by another user. Try again.


This is disk X of the backup. Please insert backup disk Y.

The wrong diskette was inserted during a Restore operation. The disks must be accessed in the same sequence as when they were produced during the Backup operation.


This is not a conditional invocation line. -- Reposition start point.

This message is issued when an attempt to specify an additional conditional invocation line fails because the conditional terminator (the diamond shaped one) was not chosen. To associate another conditional invocation line to a preexisting conditional terminator, select the conditional terminator with the Line Settings function on the Options menu. Now point to the middle of a preexisting conditional terminator and select it as the start point of the line. Next choose the appropriate module as the endpoint of the line. A second conditional invocation line will be drawn as if it were emanating from the conditional terminator you selected as the start point. In fact, there are two conditional-terminated invocation lines with the conditional terminators exactly superimposed on each other. Either can be moved or deleted separately from the other.


This item cannot be deleted or modified.

The text caption which appears on diagrams generated by the Educational Version of the Workbench cannot be altered or removed.


This operation would exceed the 600 diagram limit.

The New Diagram, Nest or Page operation you requested would cause more than the 600 diagrams per diagram type limit for this project to be exceeded and the operation cannot be completed.


This page already contains the maximum of 150 text items per page.
This page already contains the maximum of 750 text items per page.

You are allowed up to 200 blocks of text on a diagram.


This page already contains the maximum of 200 lines per page .
This page already contains the maximum of 500 lines per page .

You are allowed to have any combination of 500 lines and line segments on a diagram.


This page already contains the maximum of 100 symbols per page.
This page already contains the maximum of 250 symbols per page.

A diagram may contain up to 250 symbols. Once this maximum is reached, you can't add more. Try subdividing the diagram.


This PERFORM statement is generated from an invocation line.

You have specified that module description fields are to be interpreted as COBOL code and placed into your generated shell code. Therefore, the PERFORM statements that would otherwise be generated from module invocations appearing on structure chart diagrams will not be used as generated code. Rather, they will be placed in the code as comments for your reference, to compare against the code stored in the module description field.


This project is stored on a local drive to which you do not have access.

The selected project is stored on a local drive on another workstation. You must be using that station in order to access the project, even if you have been given rights.


Too many flows to fit on diagram. -- Remaining flows ignored.

This message is displayed by the Nest and Split Data Flow operations. When splitting a data flow, there was not enough space in the margin to draw all the subflows. Therefore, only the subflows specified before this message appeared will be drawn in the diagram's margin. If you wish to continue splitting the parent data flow, move the flows on the margin (either individually or in a block) about two inches toward the middle of the diagram and once again select Split. Now select one of the subflows as the object of the Split. The split operation will further decompose the parent data flow, not the subflow. Then enter or select the component subflows. Repeat this procedure until you have fully decomposed the parent data flow.

The instructions for the Nest operation are similar. Follow the above instructions to move the flows on the margin(s) of the child diagram. Then, Save the diagram and return to the parent diagram using the Parent option of the Nest function. The parent diagram containing the nested process should be the current diagram. Now locate the nested process and renest this parent process using the Nest Explode operation. Another set of data flows will be dragged down and drawn on the child diagram. Repeat this procedure until the message is no longer displayed.


Too many parameters.

There are too many parameters in the 'params' clause of a custom report specification.


Too many reports.

You have already saved the maximum number of custom reports. You cannot save another.


Tree file already exists in this subdirectory -- Select another path.

The subdirectory to which you are moving the project already contains the current project tree file.


Trigger "X" already in repository. Add to Table?

You tried to add a trigger to the repository that is already there. If you want to attach it to the current table (entity), press  Ok. Otherwise, press Cancel.


Type for couple "X" cannot be determined.

The element related to by couple "X" has no physical characteristics defined.


Unable to access path\file.

Problem accessing a file in the specified directory. You might not have rights to the directory.


Unable to delete directory.

The directory containing the project you are deleting cannot be deleted. You might not have rights to the directory or the directory might not be empty.


Unbalanced braces in composition of "X".

The curly braces in the composition field of repository item "X" are not balanced.


Unbalanced parentheses.

The parentheses in an expression are not balanced.


Unexpected eof.

An end-of-file was encountered in the REPORTS.TBL file where other report definition statements were expected. Please correct the file and try again.


Unexpected error during VA operation.

Critical error, contact Visible Systems.


Unknown column "X".

The column name you entered in a 'where' clause restriction is invalid. Please consult the manual and enter a correct value.


Unknown parameter "X".

The parameter you entered in a 'where' clause restriction is does not match any parameter expression you entered in the 'params' clause. Please enter a correct value.


User file cannot be accessed if security is disabled.

The Users option on the Utilities menu cannot be selected if security is not enabled. To enable security in the single user version of the Workbench, select the Security option from the Options menu and enter a USER ID of SUPERVISOR. This will enable security and prevent unauthorized users from entering the Workbench. After enabling security, the supervisor can assign a password for the USER ID of SUPERVISOR. To disable security, sign on as SUPERVISOR and deselect Security.


User not logged on.

NetWare checked its list of actice USER IDs is checked and the one you used is not among them. You can't send a message to a user who is not logged in.


VR Repository Access Error (Error Displays as a Dialog Box)

The message usually occurs because the data repository and diagram parameter files have become unsynchronized due to a latent problem or power loss during a Workbench operation. It could also happen because one or more repository files has become unavailable due to deletion. There are other possible causes, as well.

Since it indicates a serious problem, we recommend that you call Visible Systems so that we can help you correct the situation. It is important that you record the other information that appears in the dialog box. A simple way to do this is to press Alt-PrintScreen and capture the dialog box to the Windows Clipboard. You can then open Windows' Write program (or another software package that can deal with bitmaps). Once in Write (or whatever other software you choose), select Paste from the program's Edit menu and the image from the Clipboard will appear. Then you can select Print from the File menu and print it, so that you can refer to it when you talk to Visible Systems' technical support personnel.


Warning: "X" in composition field has an invalid type for this object.

You have entered a name in the composition field of "X" whose type cannot be used for object "X".


Warning: "X" in composition field is referenced by another cluster.

You have entered an entity into the composition field of a cluster which is already in the composition of another cluster. No entity may be referenced by more than one cluster. To select from the free entity pool (entities not referenced by any cluster), position the cursor in the composition field of the cluster and press the repository Search button. Multiple entities can be selected from the repository search dialog box.


Warning: A pure virtual method should not have a definition.  Continue?

If a class method is defined as pure virtual, or abstract, the Module Description field should be empty because pure virtual methods never get executed. They are meant to be defined by derived classes.


Warning: both Related To and Values & Meanings contain information.

It may be redundant to specify information in the Values & Meanings field when a couple is related to an element, data structure, data flow or file. We suggest you specify information in the Related To field when a couple represents a data flow diagram element, data structure, etc., and remove any information from the Values & Meanings field.

In other instances, when the couple only exists within the context of the structure chart diagram and bears no meaning in terms of a project's data flow diagrams, then the Values & Meanings field should describe this couple. For example, a control couple which signals an end of file condition would likely contain in formation in its Values & Meanings field because a condition or signal should not be defined in a data flow diagram.


Warning: Related To entry "X" does not exist in the repository.

A label was entered into the Related To field which does not reference a repository entry. Correct the spelling of the label. To determine the correct spelling of the label, execute a repository search.


Warning: Relationship "XrY" omitted from schema because it doesn't appear on the included view(s).

The named relationship either joins two entities (somewhere in this project) or is attached to an entity included in the current schema but does not appear on any of the views you chose to include in this schema. Therefore, it is omitted from the schema you are generating. If this is not what you want, add one of the views containing it to the list for the schema generation.


Warning: Relationship "XrY" omitted from schema because Entity "Z" doesn't appear on the included view(s).

The named relationship is attached to Entity "Z", which is included in the current schema but does not appear on any of the views you chose to include in this schema. Therefore, it is omitted from the schema you are generating. If this is not what you want, add one of the views containing it to the list for the schema generation.


Warning: This entry type is normally related to a data element.

A label was entered into the Related To field of a control couple which does not refer to a data element. A control couple represents an item used to coordinate the processing between procedures. In most instances, it is a single conditional signal. The Related To field should only contain an element reference due to the data flow diagraming restriction which prevents the definition of conditionals and the elementary nature of a control couple.


Warning: This entry type is normally related to a process.

A label was entered into the Related To field of a structure chart module entry which does not refer to a data flow process. A structure chart module represents the encoding of one or more data flow processes. Therefore, the Related To field should contain a label which references a process.


Warning: This entry type is normally related to an element, data structure, data flow, or
Warning: This entry type is normally related to an element, data structure, data flow, or file.

A label was entered into the Related To field of a data or generic couple which does not refer to a data element, data structure, data flow or file. A data or generic couple represents the data items passed between structure chart modules. These data items are inputs furnished to and the outputs produced by the modules. A high correlation exists between the data flow diagram entry types such as an element, data structure, etc., and a data or generic couple because the structure chart is derived from the data flow diagrams of the project.


You do not have rights to this directory.

Either you have not been assigned as a trustee to the directory selected or you have insufficient rights in the directory. There are two other ways this error could be caused. First, either the network drive mappings have changed since directory rights have been assigned. Second, some users are attempting to access this network volume with different a drive mapping than other users.

Trustee assignment is accomplished through NetWare functions, normally performed by the supervisor. The following trustee's rights must be granted for the user to gain access to the project: Read, Write, Open, Create and Search.


You do not have rights to update the VAW.INI file.

In order to change user-defined attributes or objects, you must have write access to the system VAW.INI file which is stored in the directory where VA.EXE was loaded.


You have not been assigned access rights to this project.

In order to access this project, the user who created the project or a user with supervisor equivalent privileges must include your USER ID in the access list maintained by the project. Furthermore, you must be defined as a trustee of the directory containing the project either implicitly, through the cascading effect of Parental privileges or by an explicit directory entry.

To include the USER ID in the access list maintained by the project, select Users from the Utilities menu. Trustee assignment is accomplished through NetWare functions, normally performed by the supervisor. The following trustee's rights must be granted for the user to gain access to the project: Read, Write, Open, Create and Search.


You have insufficient rights to the directory where the Visible Analyst is installed.

In order to use the Visible Analyst, you must have read, write, create, and erase rights to the directory where the VAW system data files are stored. If the System Data Path was set to be different from the program directory during the install procedure, you only need to assign read rights to the program directory. Having a separate directory for programs and data gives you the most flexibility in assigning rights to control access.


You have not been assigned modify rights to this project.

The creator of this project or a supervisor has given you view-only rights. One of those people must upgrade your rights before you can make any changes to this project.


You may not use arcs and elbows for invocation lines which have couples.

Because of the way couples are drawn, you cannot add couples to these invocation lines of these types and you cannot change an invocation line with existing couples into one of these line types.


You must have exclusive rights to branch -- Another user is editing a child diagram.

When a diagram is inserted into the tree, all diagrams below it, in the same branch, could be affected. Someone is editing a diagram within the branch. Therefore, the create cannot be performed.


You must have exclusive rights to project to perform this operation.

The selected function can only be performed if you are the only user accessing the current project.


You must have rules & repository support to access this project.

The project you are attempting to open was created with a repository, and the version of the Visible Analyst that you are using does not have repository support. Contact Visible Systems to upgrade your product configuration.


You must install printers from Windows Control Panel before this function can be used.

You cannot change printers until at least one is installed and you must do this from the Windows Control Panel.


You must select an invocation line before pasting unassociated couples.

If a couple is copied to the Windows Clipboard without an associated invocation line, you must select an invocation line before performing a Paste operation so that VAW knows where to place the couple.


You must Undo changes to the current line-in-progress to change modes.

If a line is being drawn, but has not yet been completed, you must either complete the line or select Undo from the edit menu to cancel the line before you can switch to another drawing mode.


Your selection would create more than one top level diagram.
Your selection would create more than one top level diagram. Only one top level Data Flow Diagram is allowed.

Your Copy Portion or Delete Portion operation attempted to do something that would have created more than one top-level DFD. You need to reselect the diagrams involved in the operation.


Technical Support

The telephone number to reach the technical support staff of Visible Systems Corporation is:

617-890-2273

You can also contact Visible Systems via e-mail at CompuServe account 75730,2404. You can send mail accross the Internet to 75730.2404@compuserve.com.