Copyright: (C) 1992-1998 Visio Corporation
Citation: 'Visio Enterprise 5.0 Online Help, (C) 1992-1998 Visio Corporation


L1001 error message
L1001

<table> : Conceptual name of table is not defined.

Explanation:

Each table in a model must have a conceptual name.

How to fix:

Enter a conceptual name for the table. To do so, double-click the table, click the Definition tab, then enter a new Conceptual Name.


L1003 error message
L1003

<table> : Physical name of table is not defined.

Explanation:

Each table in a model must have a physical name.

How to fix:

Enter a physical name for the table. To do so, double-click the table, click the Definition tab, then enter a new Physical Name.


L1004 error message
L1004

<table> : Physical name of table is not unique within its name space.

Explanation:

Two tables in the same name space cannot have the same physical name.

How to fix:

Enter a different physical name for the table or assign the table to a different name space. To do so, double-click the table, click the Definition tab, then enter either a different Physical Name or a new Name Space.


L1005 error message
L1005

<table> : Table has no columns defined.

Explanation:

Each table in a model must have at least one primary key column.

How to fix:

Insert one or more columns into the table and assign one of them to be a primary key. To do so, right-click the table, choose Edit Columns, then click Add. Then, right-click the table, click the Primary ID tab, then move a column from the Available Columns list to the Primary ID Columns list.


L1006 error message
L1006

<table>: Table has no primary key defined.

Explanation:

Each table in a model must have at least one primary key column.

How to fix:

Assign a column to be a primary key. To do so, double-click the table, click the Primary ID tab, then move a column from the Available Columns list to the Primary ID Columns list.


L1007 error message
L1007

<table1> : Table has an illegal circular relationship with table <table2>.

Explanation:

<table1> is either directly or indirectly a parent of <table2> or vice-versa. Circular relationships are only allowed if one of the relationships involved is non-identifying.

How to fix:

Make one of the relationships non-identifying or remove one of the relationships from the model. To make a relationship non-identifying, double-click the relationship, then click the Misc. tab and set the Relationship Type to Non-Identifying. To remove a relationship, click to select it, then press Delete.


L1008 error message
L1008

<table>: Derived table is not allowed to have a primary key. The primary key is inherited from the base table.

Explanation:

A table derived from another table inherits the primary key of the base table and cannot have a separate primary key.

How to fix:

Remove the primary key columns from the derived table. To do so, double-click the table, click the Primary ID tab, then move the columns from the Primary ID Columns list to the Available Columns list.


L1009 error message
L1009

<table1> Circular relationship with table <table2> is not recommended.

Explanation:

<table1> is either directly or indirectly a parent of` <table2> or vice-versa, but one of the relationships is non-identifying, which makes the circular relationship legal. This usually indicates the need to remove one of the relationships from the model.

How to fix:

Remove one of the relationships from the model. To do so, click to select the relationship, then press Delete.


L1010 error message
L1010

<table> : Conceptual name of table is not unique within its name space.

Explanation:

Two tables in the same name space cannot have the same conceptual name.

How to fix:

Enter a different conceptual name for the table or assign the table to a different name space. To do so, double-click the table, then click the Definition tab and either enter a new Conceptual Name or a new Name Space.


L1013 error message
L1013

<table> : Multiple inheritance is not allowed between tables.

Explanation:

One table cannot be directly derived from two or more other tables.

How to fix:

Remove one or more of the inheritance relationships. To do so, click to select the inheritance relationship, then press Delete.


L2001 error message
L2001

<column> : Conceptual name of column is not defined.

Explanation:

Each column in a table must have a conceptual name.

How to fix:

Enter a conceptual name for the column. To do so, right click the table containing the column, choose Edit Columns, select the offending column, then click Edit. Click the Definition tab, then enter a Conceptual Name.


L2003 error message
L2003

<column> : Physical name of column is not defined.

Explanation:

Each column in a table must have a physical name.

How to fix:

Enter a physical name for the column. To do so, right click the table containing the column, choose Edit Columns, select the offending column, then click Edit. Click the Definition tab, then enter a Physical Name.


L2004 error message
L2004

<column> : Physical name of column is not unique.

Explanation:

Two columns in the same table cannot have the same physical name.

How to fix:

Change the physical name of the column. To do so, right click the table containing the column, choose Edit Columns, select the offending column, then click Edit. Click the Definition tab, then enter a different Physical Name.


L2006 error message
L2006

<column> : Primary key column that allows null values is not recommended.

Explanation:

Primary keys are required and must contain unique identifying values. Null values generally indicate optional columns. Allowing a null value in a primary key is legal but it is not recommended.

How to fix:

Change the column so that it does not allow null values or remove the column from the list of primary keys for that table. To change the column’s attributes, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Definition tab then uncheck Allow Null Values. To remove the column from the list of primary keys, double-click the table, click the Primary ID tab, then move the offending column from the Primary ID Columns list to the Available Columns list.


L2007 error message
L2007

<column> : Conceptual name of column is the same as table <table>.

Explanation:

A column and a table cannot both have the same conceptual name because they cannot represent the same conceptual object or entity. Two columns can share the same conceptual name if they represent the same conceptual object or entity.

How to fix:

Rename either the column or the table. To rename the column, right-click the table containing the column, choose Edit Columns, select the offending column, then click Edit. Click the Definition tab, then enter a different Conceptual Name. To rename the table, double-click it, click the Definition tab, then enter a new Conceptual Name.


L2008 error message
L2008

<column1> : Column has same conceptual name as column <column2> but has a different data type.

Explanation:

If two columns describe the same attribute and share the same conceptual name they must also have the same data type.

How to fix:

Change the data type of the offending column. To do so, right-click the table containing the column, choose Edit Columns, select the offending column, then click Edit. Click the Data Type tab, then specify the same data type as used by the other column.


L2009 error message
L2009

<column1> : Column has identical conceptual name and name space as Column <column2>.

Explanation:

<column1> and <column2> share the same conceptual name while existing in the same name space.

How to fix:

Rename either column. To do so, right-click the table containing the column, choose Edit Columns, select the offending column, then click Edit. Click the Definition tab, then enter a new Conceptual Name.


L3001 error message
L3001

<relationship> : Parent column(s) not specified.

Explanation:

A foreign key relationship was created but either no parent columns were specified or one or more parent columns were not associated with their respective child columns.

How to fix:

Associate child columns with the correct parent columns. To do so, double-click the relationship, click the Definition tab, then associate columns from the parent table with columns in the child table.


L3002 error message
L3002

<relationship> : Child column(s) not specified.

Explanation:

A foreign key relationship was created but either no child columns were specified or one or more child columns were not associated with their respective parent columns.

How to fix:

Associate child columns with the correct parent columns. To do so, double-click the relationship, click the Definition tab, then associate columns from the parent table with columns in the child table.


L3003 error message
L3003

<relationship> : Parent column(s) cannot be a subset of the primary key.

Explanation:

The parent columns in this foreign key relationship must represent the entire primary key of the parent table.

How to fix:

Modify the column associations for that relationship so that the parent columns represent the entire primary key or remove the parent columns from the primary key. To modify column associations, double-click the relationship, click the Definition tab, then associate or disassociate columns. To remove columns from the primary key, double-click the table, click the Primary ID tab, then remove columns from the Primary ID Columns list.


L3004 error message
L3004

<column1> : Foreign key column data type not consistent with parent column <column2> data type.

Explanation:

The data types of the child columns and parent column in a foreign key relationship are not the same. Referential integrity cannot be guaranteed.

How to fix:

Modify the data type of either column. To do so, right-click the table containing the column, choose Edit Columns, select the offending column, then click Edit. Click the Data Type tab, then assign the same data type used by the other column.


L3005 error message
L3005

<relationship> : The number of parent columns is different than the number of child columns.

Explanation:

One or more parent columns in this foreign key relationship has no association with a respective child column.

How to fix:

Associate all parent columns with their child columns. To do so, double-click the relationship, click the Definition tab, then associate columns from the parent table with their respective columns in the child table.


L3006 error message
L3006

<relationship> : Child column(s) <column1> allows null values that are not allowed in foreign key parent column(s) <column2>.

Explanation:

The Allow Null Values setting for child columns in a foreign key relationship must either match those in the parent columns or all child columns must Allow Null Values. For example, a parent table’s primary key contains two columns, and neither allows null values. If one of these foreign key columns in the child table allows null values and the other does not, this error will be generated.

How to Fix:

Change the child column’s Allow Null Values setting to match that of the parent column or change all child columns to Allow Null Values. To do so, right-click the table containing the column, choose Edit Columns, select the offending column, then click Edit. Click the Definition tab, then check or uncheck Allow Null Values.


L3007 error message
L3007

<relationship> : Parent column <column1> allows null values but child column <column2> does not.

Explanation:

The parent column is set to Allow Null Values but the child column is not. Referential integrity cannot be guaranteed.

How to fix:

Change the child column’s Allow Null Values setting to match that of the parent column. To do so, right-click the table containing the column, choose Edit Columns, select the offending column, then click Edit. Click the Definition tab, then uncheck Allow Null Values.


L3008 error message
L3008

<column> : Referential Integrity Set Null option is not valid when child column '%s' does not allow null values.

Explanation:

The On Update / On Delete Set Null referential integrity option for this foreign key relationship contradicts the Allow Null Values setting of a child column. Referential integrity cannot be guaranteed.

How to fix:

Change the child column to allow null values or change the referential integrity option for On Update / On Delete to something other than Set Null. To set the child column to allow null values, right-click the table containing the column, choose Edit Columns, select the offending column, then click Edit. Click the Definition tab, then check Allow Null Values. To change referential integrity settings, double-click the relationship, click the Ref. Integrity tab, then set options.


L3009 error message
L3009

<relationship> : Referential integrity On Update Set Null option is invalid when the foreign key cardinality does not allow null values.

Explanation:

The On Update Set Null referential integrity option for this foreign key relationship contradicts the cardinality of the foreign key. Referential integrity cannot be guaranteed.

How to fix:

Change the cardinality of the foreign key. To do so, double-click the relationship, click the Ref. Integrity tab, then change the referential integrity option for On Update to something other than Set Null.


L3010 error message
L3010

<relationship> : Referential integrity On Delete Set Null option is invalid when the foreign key cardinality does not allow null values.

Explanation:

The On Delete Set Null referential integrity option for this foreign key relationship contradicts the cardinality of the foreign key. Referential integrity cannot be guaranteed.

How to fix:

Change the cardinality of the foreign key. To do so, double-click the relationship, click the Ref. Integrity tab, then change the referential integrity option for On Update to something other than Set Null.


L3011 error message
L3011

<relationship1> : Child columns overlap with child columns of <relationship2>.

Explanation:

One or more child columns of <relationship1> is also a child column of <relationship2>.

How to fix:

Remove or redefine one of the offending foreign key relationships. To remove the relationship, click to select it then press Delete. To redefine the relationship, double-click it, then click the Definition tab.


L3012 error message
L3012

<relationship> : Cardinality Zero-or-One-to-One-or-More or Zero-or-One-to-Exactly-N is highly unusual.

Explanation:

A foreign key relationship with a parent column set to allow null values and a child column that does not allow null values is not recommended. Referential integrity cannot be guaranteed.

How to fix:

Change the cardinality of the foreign key relationship. To do so, double-click the relationship, click the Misc. tab, then set Cardinality options.


L3013 error message
L3013

<relationship> : Relationship has a cardinality of either zero-or-one or exactly-one yet the child columns do not form a key.

Explanation:

The cardinality of the relationship implies a uniqueness constraint over the child column yet there is no such constraint.

How to fix:

Add a uniqueness constraint to the child columns of the relationship. To do so, double-click the table, click the Indexes tab, then create a new index with a unique index.


L3014 error message
L3014

<relationship1> : Foreign key relationship has same parent and child columns as <relationship2>.

Explanation:

Two identical foreign key relationships exist; only one is necessary.

How to fix:

Remove one of the relationships. To do so, click to select it, then press Delete.


L3015 error message
L3015

<relationship> : Category relationship cannot be non-Identifying.

Explanation:

The child entity in a category relationship must have a primary key that is identical to the primary key of the parent entity.

How to fix:

Move the relationship attribute(s) in the child entity to the primary key or change the category relationship to a non-identifying relationship. To make a column part of a primary key, double-click the table, click the Primary ID tab, then move the column to the Primary ID Columns list. To make a category relationship non-identifying, double-click the relationship, then click the Misc. tab.


L3016 error message
L3016

<column> : Non-primary parent column in <relationship> must exist as an alternate key.

Explanation:

Parent columns in a foreign key relationship must uniquely identify the parent table. If the parent columns are not the primary key they must be an alternate key.

How to fix:

Create an alternate key on the parent column(s) or move the offending column into the primary key area of the parent table. To do so, double-click the table, then click the Primary ID tab.


L3017 error message
L3017

Relationship has cardinality other than either zero-or-one or exactly-one, yet the child columns form a key.

Explanation:

Since the child columns are constrained to be unique, the cardinality of the relationship must be either zero-or-one or exactly-one. Since the cardinality of the relationship permits duplicate children it is likely to be incorrect.

How to fix:

Change the cardinality of the relationship to either zero-or-one or exactly-one. To do so, double-click the relationship, then click the Misc. tab.


L3018 error message
L3018

<relationship> : Parent column <column1> and child column <column2> have mismatched value/range constraints.

Explanation:

Two columns that are connected by a foreign key relationship must have the same set of allowable values or referential integrity cannot be guaranteed.

How to fix:

Change either column’s value/range configuration. To do so, double-click the relationship, then click the Check tab.


L3019 error message
L3019

Relationship has a cardinality of either zero-or-one or exactly-one yet the child columns form part of a key.

Explanation:

The relationship targets part of a key and has cardinality zero-or-one or exactly-one. If this is the case, either the child columns form the true key and the rest of the columns in the key are redundant or the cardinality of the relationship is incorrect.

How to fix:

Change the cardinality on the relationship. To do so, double-click the relationship, then click the Misc. tab.


L3020 error message
L3020

<relationship1> : Foreign key relationship has same parent and child tables as <relationship2> but does not have different forward and inverse verb phrases.

Explanation:

Two relationships between the same two tables that are described by the same forward and inverse verb phrases cannot be uniquely identified.

How to fix:

Change the verb phrase of one of the relationships or remove one of the relationships. To change a relationship’s verb phrase, double-click the relationship, then click the Name tab. To remove a relationship, click to select it, then press Delete.


L3021 error message
L3021

<relationship> : Category relationship must be from the parent primary key to the child primary key and both primary keys must be the same size.

Explanation:

Category relationships represent an inheritance relationship between a parent entity and a child entity. A child entity in a category relationship must inherit the same primary key as that of its parent.

How to fix:

Move the affected columns in the child entity to the primary key or change the category relationship to a non-identifying relationship. To make a column part of a primary key, double-click the table, click the Primary ID tab, then move the column to the Primary ID Columns list. To make a category relationship non-identifying, double-click the relationship, then click the Misc. tab.


L3022 error message
L3022

<relationship> : Self-referencing foreign key column <column> cannot exist as both a parent and a child in the same relationship.

Explanation:

A self-referencing foreign key relationship contains a column listed as both a parent column and a child column. This is invalid.

How to fix:

Change the relationship’s definition. To do so, double-click the relationship, then click the Definition tab.


L3023 error message
L3023

<relationship> : Foreign key relationship contains a duplicate child column <column>.

Explanation:

A foreign key relationship is not allowed to contain a child column that is associated with more than one parent column in the same relationship.

How to fix:

Change or remove the association between the offending child column and the respective parent column. To do so, double-click the relationship, then click the Definition tab.


L3024 error message
L3024

<relationship> : Foreign key relationship contains a duplicate parent column <column>.

Explanation:

A foreign key relationship is not allowed to contain a parent column that is associated with more than one child column in the same relationship.

How to fix:

Change or remove the association between the offending child column and the respective parent column. To do so, double-click the relationship, then click the Definition tab.


L3025 error message
L3025

<column>: Child column in foreign key '%s' cannot be a subfield of a composite type.

Explanation:

A child column in a foreign key relationship is a subfield of domain type, distinct type or row type. Composite types inside of keys or foreign key relationships are not supported.

How to fix:

Remove the column from the foreign key relationship. To do so, double-click the relationship, then click the Definition tab.


L3026 error message
L3026

<column> : Parent column in foreign key '%s' cannot be a subfield of a composite type.

Explanation:

A parent column in a foreign key relationship is a subfield of a domain type, distinct type, or row type. Composite types inside of keys or foreign key relationships are not supported.

How to fix:

Remove the column from the foreign key relationship. To do so, double-click the relationship, then click the Definition tab.


L3027 error message
L3027

Foreign key relationship cardinality minimum is greater than the maximum.

Explanation:

The relationship cardinality can never be satisfied if the minimum cardinality exceeds the maximum cardinality. For example, no number can be more than 17 and less than 15.

How to fix:

Change the minimum and maximum cardinality. To do so, double-click the relationship, then click the Misc. tab.


L4001 error message
L4001

<index1>: Index on table <table> and Index <index2> on the same table are identical.

Explanation:

Two indexes on this table are identical. This is usually caused by an oversight.

Note: Some DBMSs create indexes automatically, but hide them from the user. For example, Microsoft Access creates an index for every foreign key but the index is not visible to the user.

How to fix:

Remove one of the indexes. To do so, double-click the table, then click the Indexes tab.


L4002 error message
L4002

<index> : Index on table <table> has no columns defined.

Explanation:

An index was created on this table, but no columns were inserted into it.

How to fix:

Remove the index or add columns to it. To do so, double-click the table, then click the Indexes tab.


L4003 error message
L4003

<index> : Alternate key on table <table> is identical to primary key.

Explanation:

An alternate key cannot be identical to the primary key.

How to fix:

Remove the alternate key or modify its column list so that it is no longer identical to that of the primary key. To do so, double-click the table, then click the Indexes tab.


L4004 error message
L4004

<index> : Alternate key on table <table> cannot be the same as or a part of the primary key.

Explanation:

The columns of an alternate key cannot be contained in the primary key.

How to fix:

Remove the alternate key or add one or more non-primary columns to the alternate key’s column list. To do so, double-click the table, then click the Indexes tab.


L4005 error message
L4005

<index1> : Alternate key on table <table> and alternate key <index2> (on same table) are functionally identical.

Explanation:

<index1> contains a superset of <index2>’s columns making it functionally similar to but less optimal than <index2>.

How to fix:

Remove <index1> or modify one of the redundant indexes so that the <index2> is no longer a subset of <index1>. To do so, double-click the table, then click the Indexes tab.


L4006 error message
L4006

<table>: Primary key on table '%s' cannot be a subset of an alternate key.

Explanation:

A primary key cannot be wholly contained within an alternate key. For example, if you have the table Person and define the primary key to be ssn, you cannot then define an alternate key of ssn and lname.

How to fix:

Ensure that the primary key is not wholly contained inside an alternate key. To do so, double-click the table, then click the Primary ID tab.


L4007 error message
L4007

<column> : Primary key on table '%s' cannot contain subfields of a composite type.

Explanation:

A column in a primary key is a subfield of domain type, distinct type, or row type. Composite types inside of keys or foreign key relationships are not supported.

How to fix:

Remove the offending column from the primary key. To do so, double-click the table, then click the Primary ID tab.


L4008 error message
L4008

<column> : Index on table '%s' is not allowed to contain subfields of a composite type.

Explanation:

A column in an index is a subfield of a domain type, distinct type, or row type. Composite types inside of keys or foreign key relationships are not supported.

How to fix:

Remove the column from the index. To do so, double-click the table, then click the Indexes tab.


L5001 error message
L5001

<table>: Table has category that does not have a discriminator.

Explanation:

Category relationships are meaningless without a discriminating attribute that distinguishes one subcategory from another.

How to fix:

Select a discriminator attribute on the parent table. To do so, double-click the category, then click the Definition tab.


L5002 error message
L5002

<table> : Category is marked as complete, but has only one variation.

Explanation:

Complete category relationships usually involve more than one subcategory.

How to fix:

Make the category relationship incomplete or add more child tables. To set the category to incomplete, double-click the category, then uncheck Category Is Complete. To add more tables, drag entity shapes to the drawing page, then use the Category To Child shape to connect them to the category.


L5003 error message
L5003

<table> : Table has duplicate category with discriminator <column>.

Explanation:

Two categories use the same discriminator attribute and therefore are redundant.

How to fix:

Remove one of the categories, then merge its subcategory entities with the remaining category.


L6000 error message
L6000

<distinct type>: Distinct type aliases more than one type.

Explanation:

A distinct type can alias only one type.

How to fix:

Remove the invalid distinct type or change it to alias a single named type. To remove the type, click to select it, then press Delete. To change the type alias, double-click the type and click the Aliased Type tab.


L6001 error message
L6001

<distinct type> : Distinct type aliases an unnamed row.

Explanation:

A distinct type can only alias a named type.

How to fix:

Remove the invalid distinct type or change it to alias a single named type. To remove the type, click to select it, then press Delete. To change the type alias, double-click the type and click the Aliased Type tab.


L6002 error message
L6002

<domain> : Domain type must alias a built-in type, collection type, or unnamed row type.

Explanation:

A domain type can only alias a built-in type, collection type, or an unnamed row type.

How to fix:

Remove the invalid domain type or select a new aliased type. To remove the type, click to select it, then press Delete. To change the type alias, double-click the type and click the Aliased Type tab.


L6003 error message
L6003

<named row type> : Named row type has no fields defined.

Explanation:

A named row type must contain at least one field.

How to fix:

Insert a field into the type or remove the type. To insert a field, right-click the type, choose Edit Fields, then click Add. To remove a type, click to select it, then press Delete.


L6004 error message
L6004

<unnamed row type> : Unnamed row type has no fields defined.

Explanation:

A named row type must contain at least one field.

How to fix:

Insert a field into the type or remove the type. To insert a field, right-click the type, choose Edit Fields, then click Add. To remove a type, click to select it, then press Delete.


L6005 error message
L6005

<type>: Type name is not unique.

Explanation:

A type was defined with a name that is already used by another type. Two types cannot share the same name.

How to fix:

Remove or rename the duplicate type. To remove a type, click to select it, then press Delete. To rename a type, double-click it, then click the Definition tab. If the duplicate type is a user-defined type, choose Database > User-Defined Types, then rename or remove it.


L6006 error message
L6006

<type>: Type inheritance can only exist between named row types.

Explanation:

A type inheritance relationship exists between two types, and one of the types is a domain type or a distinct type. Type inheritance can only exist between two named row types.

How to fix:

Remove the type inheritance relationship or recreate the domain type or distinct type as a named row type. To remove a type inheritance relationship, click to select it, then press Delete.


L6007 error message
L6007

<field> : Single row type field allows null values.

Explanation:

A row type consists of only one field that allows null values. This is not preferred.

How to fix:

Change the field so that it does not allow null values. To do so, right-click the shape, choose Edit Fields, select the offending field, then click Edit. Click the Definition tab, then uncheck Allow Null Values.


L6008 error message
L6008

<type> : Aliased type cannot allow null values.

Explanation:

A domain type or distinct type aliases another type which allows null values. This is not preferred.

How to fix:

Uncheck Allow Null Values for the aliased type from where it is aliased.


L7000 error message
L7000

<field>: Physical name of field is not unique.

Explanation:

Two fields in a row type cannot share the same physical name.

How to fix:

Remove or rename the duplicate field. To do so, right-click the type, choose Edit Fields, then select the offending field. To remove it, click Remove. To rename it, click Edit, click the Definition tab, then enter a new name.


L7001 error message
L7001

<type> : A composite type originating from a logical document cannot be associated with objects built from different documents.

Explanation:

A row type, distinct type, or domain type was created in a logical model in a project and then referenced in another type or table that originated from another source document. Cross-document references of types are not supported.

How to fix:

Make sure the two connected objects originate from the same document by moving one of them into the other document.


M1010 error message
M1010

<type> : User-defined types from multiple source documents conflict.

Explanation:

User-defined types must be consistent among documents.

How to fix:

Make user-defined types identical. To do so, choose Database > User-Defined Types.


M1011 error message

M1011

Subtype has conflicting primary supertype.

Explanation:

An object type that is a subtype can only have one primary supertype.

How to fix:

Make one of the subtype/supertype relationships non-primary.


M2004 error message
M2004

Cannot open model.

Explanation:

At least one model needed to build this project was unavailable. It may be open by another application or instance of Visio® Enterprise.

How to fix:

Close the other instance of the model(s).


duplicate—one needs a different number


P1000 error message
P1000

<type name> : Type name exceeds the maximum number of characters.

Explanation:

The type name exceeds the number of characters allowed by the target DBMS.

How to fix:

Shorten the type name. To do so, double-click the type, click the Definition tab, then enter a shorter name.


duplicate—one needs a different number


P1000 error message
P1000

<table name> : Physical name exceeds the maximum number of characters.

Explanation:

The table’s physical name exceeds the number of characters allowed by the target DBMS.

How to fix:

Shorten the table’s name. To do so, double-click the table, click the Definition tab, then enter a shorter Physical Name.


Duplicate error--See P4004 & 4604. P1001 is preferred.


P1001 error message
P1001

<table name> : Physical name is a reserved word in the target DBMS.

Explanation:

The table name conflicts with a reserved word in the DBMS. Examples of reserved words include ‘Select,’ ‘Table,’ and ‘Create.’ Check the documentation of the target DBMS for a list of reserved words.

How to fix:

Choose a different table name. To do so, double-click the table, click the Definition tab, then enter a new Physical Name.


P1002 error message
P1002

<table name> : First character in the table name is not valid for the target DBMS.

Explanation:

The first character in the table name is not allowed in the target DBMS. Examples of invalid characters include ‘#’ or ‘$’ or ‘@.’ Check the documentation for the target DBMS for a list of invalid initial characters.

How to fix:

Remove the invalid character that begins the table name and replace it with a valid choice. To do so, double-click the table, click the Definition tab, then enter a new Physical Name.


duplicate error—see P4606. P1003 is preferrred.


P1003 error message
P1003

<table name> : Table name contains character(s) that are invalid for the target DBMS.

Explanation:

The table name contains characters not allowed in the target DBMS. Examples of invalid characters include ‘#’ or ‘$’ or ‘%.’ Check the documentation for the target DBMS for a list of invalid characters.

How to fix:

Remove the invalid character in the table name and replace it with a valid choice. To do so, double-click the table, click the Definition tab, then enter a new Physical Name.


P1004 error message
P1004

<table name> : Too many columns defined in the table for the target DBMS.

Explanation:

The target DBMS only allows a specific number of columns to be defined for a table. Check the documentation for the target DBMS for specific limits.

How to fix:

Change the number of columns to the number allowed by the target DBMS. To do so, right-click the table, choose Edit Columns, then select the columns to delete and click Remove.


P1005 error message
P1005

<table name> : Row size in the table exceeds the maximum size (<number>) allowed by the target DBMS.

Explanation:

The total of all the column lengths in the table exceeds the maximum size allowed for a table as whole. Check the documentation for the target DBMS for specific limits.

How to fix:

Adjust the table row size.


P1006 error message
P1006

<table name> : Too many indexes defined in the table. Maximum allowed is <number> for the target DBMS.

Explanation:

The number of indexes defined on the table exceeds the maximum number allowed for the target DBMS. Check the documentation for the target DBMS for specific limits.

How to fix:

Change the number of indexes to the number allowed by the target DBMS. To do so, double-click the table, click the Indexes tab, then select indexes to remove and click Delete.


P1007 error message
P1007

<table name.column name> : Column exceeds the maximum characters (<number>) allowed by the target DBMS.

Explanation:

The column name exceeds the maximum column name length allowed by the target DBMS. Check the documentation for the target DBMS for specific limits.

How to fix:

Change the column name length to the limit allowed by the target DBMS. To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Definition tab and enter a shorter name.


Duplicate error--See P4700. P1008 is preferred.


P1008 error message
P1008

<table name.column name> : Column name is a reserved word in the target DBMS.

Explanation:

The column name conflicts with a reserved word in the DBMS. Examples of reserved words include ‘Select,’ ‘Table,’ and ‘Create.’ Check the documentation of the target DBMS for a list of reserved words.

How to fix:

Choose a different table name. To do so, double-click the table, click the Definition tab, then enter a new Physical Name.


P1009 error message
P1009

<table name.column name> : Column name contains invalid character(s).

Explanation:

The column name contains characters not allowed in the target DBMS. Examples of invalid characters include ‘#’ or ‘$’ or ‘%.’ Check the documentation for the target DBMS for a list of invalid characters.

How to fix:

Remove the invalid character in the column name and replace it with a valid choice. To do so, right-click the table, choose Edit Column, select the offending column, then click Edit. Click the Definition tab, then enter a new Physical Name.


Duplicate error--See P4001 (next)


P1010 error message
P1010

<table name.column name> : Column data type length exceeds the maximum (<number>) allowed by the target DBMS.

Explanation:

The column length exceeds the maximum allowed by the target DBMS. For example, some DBMSs have a limit of 255 characters for a character data type. Check the documentation for the target DBMS for specific limits.

How to fix:

Change the data type length associated with the column to conform to the target DMBS limit. To do so, right-click the table, choose Edit Columns, then select the offending column and click Edit. Click the Data Type tab, then change the Length to a smaller value.


Duplicate error--See P1010 (preceding)


P4001 error message
P4001

The column’s data type length exceeds the maximum (%d) allowed by the DBMS.

Explanation:

The column length exceeds the maximum length allowed by the target DBMS. For example, some DBMSs have a limit of 255 characters for a character data type.

How to fix:

Check the documentation for the target DBMS. Change the data type length associated with the column to conform to the target DMBS limits.


P1011 error message
P1011

<table name> : Table has an index with no index name defined.

Explanation:

An index exists on the table but no index name has been defined.

How to fix:

Define an index name for the index. To do so, double-click the table, click the Indexes tab, select the index, then enter a Name.


P1012 error message
P1012

<table name> : Table has a foreign key with no foreign key name defined.

Explanation:

A foreign key exists on the table but no foreign key name has been defined.

How to fix:

Define a foreign key name for the foreign key. To do so, double-click the relationship, click the Name tab, then enter a new Physical Name.


P1013 error message
P1013

<table name> : Table has a primary key with no primary key name defined.

Explanation:

A primary key exists on the table but no primary key name has been defined.

How to fix:

Define a primary key name for the primary key. To do so, double-click the table, click the Primary ID tab, then enter a new Physical Name.


P1014 error message
P1014

<index name> : Index name in the table <table name> exceeds the maximum characters (<number>) allowed by the target DBMS.

Explanation:

The index name exceeds the maximum index name length allowed by the target DBMS. Check the documentation for the target DBMS to determine specific limits.

How to fix:

Shorten the index name length. To do so, double-click the table, click the Indexes tab, select the offending index, then click Rename.


P1015 error message
P1015

<table name> : Foreign key name in the table <table name> is a reserved word in the target DBMS.

Explanation:

The foreign key name conflicts with a reserved word in the DBMS. Examples of reserved words include ‘Select,’ ‘Table,’ and ‘Create.’ Check the documentation of the target DBMS for a list of reserved words.

How to fix:

Choose a different foreign key name. To do so, double-click the relationship, click the Name tab, then enter a new Physical Name.


P1016 error message
P1016

<table name> : Foreign key name in the table <table name> exceeds the maximum characters (<number>) allowed by the target DBMS.

Explanation:

The foreign key name exceeds the maximum length allowed by the target DBMS. For example, some DBMSs have a limit of 255 characters for a character data type. Check the documentation for the target DBMS for specific limits.

How to fix:

Change the foreign key name length to conform to the target DMBS limit. To do so, double-click the relationship, click the Name tab, then shorten the Physical Name.


P1017 error message
P1017

<table name> : Primary key name in the table <table name> exceeds the maximum primary key name length (<number>) allowed by the target DBMS.

Explanation:

The primary key name exceeds the maximum length allowed by the target DBMS. For example, a DBMS may have a limit of 30 characters for a primary key name. Check the documentation for the target DBMS to determine specific limits.

How to fix:

Shorten the primary key name length. To do so, double-click the table, click the Primary ID tab, then enter a shorter Physical Name.


Duplicate error--See P1018. 1018 prefered.


P1018 error message
P1019

<table name> : Index name in the table <table name> is a reserved word in the target DBMS.

Explanation:

The index name conflicts with a reserved word in the DBMS. Examples of reserved words include ‘Select,’ ‘Table,’ and ‘Create.’ Check the documentation of the target DBMS for a list of reserved words.

How to fix:

Choose a different index name. To do so, double-click the table, click the Indexes tab, select the offending index, then click Rename.


P1020 error message
P1020

<table name>: Foreign key in the table <table name> contains invalid character(s).

Explanation:

The target DMBS does not allow certain characters in the foreign key name. Examples of invalid characters include ‘#,’ ‘$,’ and ‘@.’ Check the documentation for the target DBMS for a list of invalid characters.

How to fix:

Remove the invalid character in the foreign key name and replace it with a valid choice. To do so, double-click the relationship, click the Name tab, then edit the Physical Name.


P1021 error message
P1021

<table name> : Primary key name in the table <table name> contains invalid character(s).

Explanation:

The target DMBS does not allow certain characters in the primary key name. Examples of invalid characters include ‘#,’ ‘$,’ and ‘@.’ Check the documentation for the target DBMS for a list of invalid characters.

How to fix:

Remove the invalid character in the primary key name and replace it with a valid choice. To do so, double-click the table, click the Primary ID tab, then edit the Physical Name.


P1022 error message
P1022

<table name> : Index name in the table <table name> contains invalid character(s).

Explanation:

The target DMBS does not allow certain characters in the index name. Examples of characters commonly not allowed in index names are special characters like ‘#,’ ‘$,’ and ‘@.’ Check the documentation for the target DBMS for a list of invalid characters.

How to fix:

Remove the invalid character in the index name and replace it with a valid choice. To do so, double-click the table, click the Indexes tab, select the offending index, then click Rename.


P1023 error message
P1023

<table name.column name> : Column is of data type <data type>. Data type <data type> is not allowed to have index on the target DBMS.

Explanation:

The target DBMS does not allow the selected data type to have an index. A data type commonly not allowed to have an index is Boolean (true/false) data type. Check the documentation for the target DBMS for details about data types that support indexes.

How to fix:

Remove the index from the column or change the data type of the column to one that allows an index. To remove the index from the column, double-click the table, click the Indexes tab, select the offending index, then click Delete. To change the data type for a column, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Data Type tab, then select a different data type.


Duplicate error number but different message—renumber?


P1024 error message
P1024

<table name.column name> : Primary key columns that allow null values are not allowed in the target DBMS.

Explanation:

A primary key helps ensure that there are no duplicates in a table. If null values are allowed to exist in the primary key, then duplicate null fields may exist. The target DBMS does not allow primary keys to be declared as null values.

How to fix:

Uncheck Allow Null Values for the primary key column, To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Definition tab, then uncheck Allow Null Values.


Duplicate error number but different message—renumber?


P1024 error message
P1024

<column> : Composite type columns are not supported by the targeted DBMS.

Explanation:

The target DBMS does not support composite types.

How to fix:

Change the data type for the column. To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Data Type tab, then select a different data type.


P1025 error message
P1025

<table name> : Index size in the table exceeds the maximum size (<number>) allowed by the target DBMS.

Explanation:

The total length of all the columns in the index exceeds the maximum size allowed by the target DBMS. Check the documentation for the target DBMS for specific limits.

How to fix:

Change the columns in the index. To do so, double-click the table, click the Indexes tab, then edit the offending index.


P1026 error message
P1026

<table name.column name> : No precision specified for column’s data type.

Explanation:

Some data types, such as decimal and money, require a precision value.

How to fix:

Specify the precision for the data type selected for the column. To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Data Type tab, then enter a Precision value.


P1027 error message
P1027

<table name.column name> : Data type <data type> has Scale value that is longer than the Precision value.

Explanation:

Scale is the number of digits to the right of the decimal point. The Scale value cannot be greater than the Precision value for this data type.

How to fix:

Change the Scale value for the data type to a number that matches or is less than the Precision value or change the Precision value to match the Scale value. To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Data Type tab, then enter a different value for Scale or Precision.


P1028 error message
P1028

<column> : Column of data type '%s' cannot have null value in the target DBMS.

Explanation:

The target DBMS does not allow the selected data type to have null values. Data types that are commonly not allowed to have null values include bit fields, counter fields, or true/false fields. Check the documentation for the target DBMS for details about data types that support null values.

How to Fix:

Change the column so that it does not allow null values. To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Definition tab, then uncheck Allow Null Values.


Duplicate error number but different message—renumber?


P1029 error message
P1029

<table> : Only one column per table is allowed to have the TIMESTAMP data type.

Explanation:

Only one column per table is allowed to have a TIMESTAMP data type.

How to Fix:

Change the data type for the second column that uses the TIMESTAMP data type. To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Data Type tab, then change the data type.


Duplicate error number but different message—renumber?


P1029 error message
P1029

<table> : The user defined type name exceeds the maximum number of characters (<number>) allowed by the target DBMS.

Explanation:

The user-defined type name exceeds the maximum name length allowed by the target DBMS. Check the documentation for the target DBMS to determine specific limits.

How to fix:

Shorten the user-defined type name. To do so, choose Database > User-Defined Types, select the offending type, then click Rename.


P1030 error message
P1030

<type> : The user defined type name is a reserved word in the target DBMS.

Explanation:

The user defined type name conflicts with a reserved word in the DBMS. Examples of reserved words include 'Select,’ 'Table,’ and 'Create.’ Check the documentation of the target DBMS for a list of reserved words.

How to fix:

Choose a different user defined type name. To do so, choose Database > User-Defined Types, select the offending type, then click Rename.


P1031 error message
P1031

<type> : The first character in the user defined type name is invalid.

Explanation:

The target DBMS does not allow certain characters as the first character for a user defined type name. Examples of invalid characters include ‘#,’ ‘$,’ and ‘@.’ Check the documentation for the target DBMS for a list of invalid characters.

How to fix:

Remove the invalid character that begins the user defined type name, then replace it with a valid choice. To do so, choose Database > User-Defined Types, select the offending type, then click Rename.


P1032 error message
P1032

<type> : The user defined type name contains invalid character(s).

Explanation:

The user defined type name contains characters that are invalid. Examples of invalid characters include ‘#,’ ‘$,’ and ‘@.’ Check the documentation for the target DBMS for a list of invalid characters.

How to fix:

Change the user defined type name. To do so, choose Database > User-Defined Types, select the offending type, then click Rename.


P1033 error message
P1033

<index name> : Index name is not unique.

Explanation:

The target DBMS prohibits duplicate index names.

How to fix:

Rename the indexes so that each has a unique name. To do so, double-click the table, click the Indexes tab, select the offending index, then click Rename.


P1035 error message
P1035

‘%s.%s’ : Unique constraint columns cannot allow null values in the target DBMS.

Explanation:

The target DBMS does not allow any unique constraint column to allow null values.

How to fix:

Remove the uniqueness constraint and any foreign keys that target the columns.


P1036 error message
P1036

<column> : Collection types are not supported by the targeted DBMS

Explanation:

The target DBMS does not support collection types.

How to fix:

Change the collection type setting for the column. To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Collection tab, then select Single Value (Column).


P1050 error message
P1050

<table name.column name>: Only one column per table is allowed to have the AUTOINC data type.

Explanation:

Only one column per table is allowed to have an AUTOINC data type.

How to fix:

Change the data type for the second column that uses the AUTOINC data type. To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Data Type tab, then change the data type.


P1701 error message
P1701

'%s.%s' : Non-nullable column added to the table will be set with default value 1.

Explanation:

Visio® Enterprise will attempt to migrate data from the current version of the table to the new version of the table. Since the new column is not nullable, Visio Enterprise sets it to a default value of 1.


P1702 error message
P1702

<table> : This table contains columns with the LONG data type, whose data cannot be preserved through the change table process. Back up this table before proceeding. Press F1 for more help.

Explanation:

The changes you have made to the table require dropping the table and recreating it with the modified definition. However, the table contains a column with a LONG data type (the data type allows the data to be arbitrarily long and could be greater than 64K). Columns of such type cannot be used in a "insert into ... select " statement.

How to Fix:

Back up the table with the columns that have LONG Data types so that the column can be repopulated.


P1703 error message
P1703

<column> : The data type for the column has been changed from '%s' to '%s.’ The data can not be migrated in some cases. Press F1 for more help.

Explanation:

You have specified that the data type for a column in the database should be changed. Some data type conversions lose information. For example, information is lost when converting a string data type such as "This is a long string" to a numeric data type or converting from a char to an int. However, if you specify such a change and your char field has characters in it, information will be lost.

If the target DBMS supports the data type conversion, Visio® Enterprise will use it and convert the data. If the target DBMS does not support the data type conversion, Visio Enterprise will leave the original data in a backup table for you to access and convert separately.

How to Fix:

Back up your database before any schema changes are made. Before you change any data types in an existing schema, determine whether a data type conversion is possible in the target DBMS, and make sure the data that exists in the database at the time of conversion will convert as you specify.


P1704 error message
P1704

'%s' : If the table contains data, you cannot add a primary key or unique index on a newly added column.

Explanation:

If a table already contains data, it might contain duplicate rows. Because a primary key and unique indexes require all rows to be unique, the DBMS cannot enforce uniqueness.

How to Fix:

If you are sure that the data in the table does not contain any duplicate values on the column(s) for which you have the primary key or unique index, ignore this warning.

If you cannot be sure, then:

1	Copy all the data to a temporary table

2	Delete the data from the original table

3	Create the primary key or unique index

4	Copy the data back from the temporary table, and allow the DBMS to enforce uniqueness.


Duplicate error--See P4000. P2000 is preferred.


P2000 error message
P2000

<table name> : <number> clustered indexes defined. Only one clustered index is allowed per table.

Explanation:

A clustered index determines the physical layout of data within the storage medium, and there can be only one criterion by which to order the data. The target DBMS allows only one clustered index per table.

How to fix:

Remove all but one clustered index. To do so, double-click the table, click the Indexes tab, select the index, then click Options. Select the driver for the target DBMS, click Change, then uncheck Cluster Index.


duplicate with p2200; p2200 prefered.


P2100 error message
P2100

<table name> : Descending index is not supported in the SQL/Sybase server. The index will be created in ascending collation sequence.

Explanation:

A descending index has been specified in the model, however, the descending index is not supported in the target DBMS. Therefore the index will be created in an ascending collation sequence.

How to fix:

Check the model and implementation requirements. The DBMS will not support a descending index. If you do not wish to see this warning again, change the index in the model to be ascending.


duplicate with p2100; p2200 prefered.


P2200 error message
P2200

<table name> : Index cannot be created with a descending order. The index will be created in ascending collation sequence.

Explanation:

A descending index has been specified in the model but is not supported in the target DBMS. The index will be created in an ascending collation sequence.

How to fix:

Change the index in the model to be ascending. To do so, double-click the table, click the Indexes tab, select the offending index, then check the Asc box in the Indexed Columns list.


P2300 error message
P2300

<table name> : Index cannot not be created with ASC and DESC collation sequence for the target DBMS.

Explanation:

Having both ASC and DESC collation sequence in the target DBMS is not allowed. For example, if there are two columns first name last name specified for an index, the target DBMS does not allow an ASC collation sequence on the first name and a DESC on last name. The index will be created based on the collation sequence defined for the first column.

How to fix:

Change the collation sequences so that they match for all of the columns in the index. To do so, double-click the table, click the Indexes tab, select the offending index, then check or uncheck all Asc boxes in the Indexed Columns list.


P2400 error message
P2400

<column> : A table can contain only one column of data type LONG and column <column> has already been defined as LONG.

Explanation:

The target DBMS only allows one column to be of type LONG.

How to fix:

Change the column data type to some type other than LONG. To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Data Type tab, then change the data type.


P3000 error message
P3000

‘%s.%s’ : Precision for numeric() and decimal() identity is too long. The maximum allowed is %d.

Explanation:

The column’s data type length exceeds the maximum length.

How to fix:

Shorten the column’s data type length. To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Data Type tab, then change the data type.


Duplicate error--See P4002 and 4200. 4200 is preferred.


P3600 error message
P3600

‘%s’ : Microsoft Access does not allow mismatched data types between child column ‘%s.%s’ and parent column ‘%s.%s’ in a foreign key relationship.

Explanation:

Parent and child column data types must match. In Microsoft Access, a foreign key field data type which points to a counter field data type must be of data type LONG.

How to fix:

Change the parent and child column data types to match or to LONG/COUNTER. To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Data Type tab, then change the data type.


P3700 error message
P3700

'%s.%s' : Microsoft Access does not support Set Null option in the referential integrity constraint.

Explanation:

There is no way to support a Set Null referential integrity constraint in Microsoft Access.

How to fix:

Change the referential integrity settings for the foreign key relationship. To do so, double-click the relationship then click the Ref. Integrity tab.


Duplicate error--See P2000. P2000 is preferred.


P4000 error message
P4000

‘%s’: %d clustered indexes defined. Only one clustered index allowed per table.

Explanation:

Informix DBMS allows only one clustered index to be defined per table. Because clustered indexing involves the physical layout of data within the storage medium, there can be only one criterion by which to order the data.

How to fix:

Turn off clustering for all but one of the table’s indexes. To do so, double-click the table, click the Indexes tab, select an index, then click Options. Click Change, then uncheck Cluster Index. Repeat for all but one index.


Duplicate error--See P4200 and 3600. 4200 is preferred.


P4002 error message
P4002

‘%s’ : Mismatched data types, precision, or scale between a child column ‘%s. %s’ and a parent column ‘%s.%s’ of a foreign key.

Explanation:

Parent and child column data types must match. Some aspect of the data type such as the data type, the precision of the data type, or the scale does not match between the parent and child column.

How to fix:

Make sure the data type, precision, and scale of both the parent and child columns match. To do so,


P4003 error message
P4003

<index> : Index constraint '%s' cannot be created because it has the same columns as the child columns of the foreign key constraint '%s.’

Explanation:

Under Informix, if the column(s) in a unique index is the same as the child columns of a FK relationship in the table, then creation of the index will fail.

How to fix:

Remove the index or change the order of the columns in the index.


Duplicate: see P1001 & 4604. P1001 is preferred.


P4004 error message
P4004

‘%s.%s’ : Invalid column name. Reserved word.

Explanation:

The target DBMS does not allow reserved words such as FROM to be used as column names since this can cause ambiguity.

How to fix:

Change the column name.


Duplicate error--See P4701. P4050 is preferred.


P4050 error message
P4050

<column> : Primary key column allows null values. The table can be created but you will not be able to insert null values into this column because it violates the primary key constraint imposed by the server.

Explanation:

The Informix Universal Server does not permit the insertion of null values into primary key columns.

How to fix:

Change the Allow Null Values setting or move the column out of the primary key. To change the setting, right-click the table, choose Edit Columns, select the offending table, then click Edit. Click the Definition tab, then uncheck Allow Null Values. To change the primary key, double-click the table, click the Indexes tab, then move the offending column from the Primary ID Columns list to the Available Columns list.


Duplicate error--See P4002 and P3600. 4200 is preferred.


P4200 error message
P4200

‘%s’ : Mismatched data types, precision, or scale between a child column ‘%s.%’ and a parent column ‘%s.%s’ of a foreign key.

Explanation:

Parent and child column data types must match. Some aspect of the data type such as the data type, precision, or scale, does not match between the parent and the child column.

How to fix:

Check the data type, precision, and scale for the parent and child columns and change them to match. To do so, right-click the table, choose Edit Columns, select the offending column, then click Edit. Click the Data Type tab, then change the data type.


P4201 error message
P4201

<column> : SQLAnywhere does not support columns in a primary key or unique index set to allow null values.

Explanation:

SQLAnywhere does not permit you to create primary keys and unique indexes based on columns that allow null values

How to fix:

Uncheck Allow Null Values or remove the column from the primary key and/or unique index. To uncheck Allow Null Values, right-click the table, choose Edit Columns, select the offending column, click Edit, then click the Definition tab. To remove a column from an index, double-click the table, click the Indexes tab, then move the column from the Primary ID Columns list to the Available Columns list.


P4450 error message
P4450

<table> : The Paradox ODBC driver does not allow table names over 8 bytes long.

Explanation:

The Paradox ODBC driver has an internal 8-character limit on table names. The Paradox DBMS does not have this limitation.

How to fix:

Switch to a different ODBC driver or generate a DDL script and then run it from within Paradox.


P4600 error message
P4600

‘%s’ : Primary key cannot be defined on a row type.

Explanation:

INFORMIX Universal Server restricts the types of columns involved in an index to be built-in types. Since a primary key will create an index, no column in a primary key can contain a row type.

How to fix:

Change the primary key to map to no key.


P4601 error message
P4601

‘%s’ : Index cannot be defined on a row type.

Explanation:

INFORMIX-Universal Server restricts the types of columns involved in an index to built-in types.

How to fix:

Remove the index. To do so, double-click the table, click the Indexes tab, select the offending index, then click Delete.


P4602 error message
P4602

‘%s’ : Table must be typed in order to participate in an inheritance relationship.

Explanation:

The implementation restricts tables using inheritance to typed tables.

How to fix:

Base the table on a type. To do so, double-click the table, then click the Definition tab. Select a type from the Defining Type list. Note that tables containing columns cannot be typed.


Huh? Beck, I can’t wrap my brain around this next one, though I have tried. This is what was there originally. Scary.


P4603 error message
P4603

<table> : Table inheritance between table ‘%s’ and table ‘%s” requires associated types to have the same inheritance relationship.

Explanation:

The implementation restricts tables using inheritance to follow the inheritance patterns of their types.

How to fix:

Base the table on a table that is based on the table’s parent type.


Duplicate: see P1001 &p4004


P4604 error message
P4604

'%s' is a reserved word and cannot be used.

Explanation:

INFORMIX-Universal Server does not allow reserved words such as FROM to be used as names since this can cause ambiguity.

How to fix:

Change the name.


Duplicate withP1003 (there used to be two identical messages—I deleted one. EW). P1003 is preferred.


P4606 error message
P4606

‘%s.%s’ : Identifier contains invalid character(s).

Explanation:

INFORMIX-Universal Server restricts the characters that can be used in a table name.

How to fix:

Change the table name.


P4607 error message
P4607

‘%s.%s’ : Ref’s are not supported.

Explanation:

INFORMIX-Universal Server does not support reference types.

How to fix:

Use foreign keys or row IDs instead.


Duplicate: see P4200


P4608 error message
P4608

‘%s’ : Mismatched data types, precision settings, or scale settings between a child column and a parent column of a foreign key.

Explanation:

The parent and child column data types must match. Some aspect of the data type such as the data type, the precision of the data type, or the scale does not match between the parent and child column.

Note: A parent column of type SERIAL (SERIAL8) may have a child column of type INTEGER (INTEGER8).

How to fix:

Change the parent and child column to the same data type, precision, and scale.


P4609 error message
P4609

<type> : Distinct type based on the type ‘%s.’

Explanation:

An INFORMIX-Universal Server distinct type cannot be based on the types LVARCHAR, SENDRECV, or IMPEX.

How to fix:

Use the data type itself instead.


Duplicate: see P1008


P4700 error message
P4700

‘%s’ is a reserved word and may result in syntactic ambiguities in SQL statements.

Explanation:

INFORMIX-Universal Server does not allow reserved words such as FROM to be used in names since this can cause an ambiguity.

How to fix:

Change the name to a word that is not reserved.


Duplicate see P4050


P4701 error message
P4701

<column> : Primary key column is declared as nullable. The table can be created but you will not be able to insert nullable values into this column because it violates the primary key constraint imposed by the server.

Explanation:

The Informix server does not permit the insertion of null values into primary key columns. This is a limitation of the Informix server, and may require you to redesign this portion of the model.

How to fix:

Using the column’s property sheet, mark the column as not nullable. Alternatively, you can move the column out of the primary key.


P4800 error message
P4800

<column> : The length of the data type exceeds the maximum length of %d.

Explanation:

The BLOB data type size exceeds the maximum permitted by IBM DB2.

How to fix:

Decrease the BLOB data type size. To do so, right-click the table, choose Edit Columns, then click the Data Type tab.


P4801 error message
P4801

<column> : Parent column of the foreign key constraint is not in the primary key column list.

Explanation:

IBM DB2 does not permit the target of a foreign key relationship to be an alternate key. The target of the relationship must be in the primary key.

How to fix:

Mark the parent column as the primary key in the parent table or enforce the intended rule with a trigger or stored procedure. To do so, double-click the table, click the Primary ID tab, then move the parent column into the Primary ID Columns list. To create a trigger or stored procedure, choose Database > View > Code Selector, then click New.


P4802 error message
P4802

<table> : Table inheritance is not supported in IBM DB2 server.

Explanation:

IBM DB2 does not support the ability to define a parent-child relationship between two separate tables.

How to fix:

Remove the table inheritance relationship and redefine it as a foreign key relationship between the primary keys of the two tables. To remove a table inheritance relationship, click to select it, then press Delete. To define a foreign key relationship, click the connector tool, then drag from the parent table to the child table. Double-click the relationship line, click the Definition tab, then associate the primary keys of the two tables.


P4850 error message
P4850

<column> : Referential integrity for On Update Cascade and On Update Set Null are not supported in the IBM DB2 server. No Action will be substituted.

Explanation:

IBM DB2 does not support Cascade or Set Null as choices for the On Update rule.

How to fix:

Change referential integrity settings or enforce the intended rule with a trigger or stored procedure. To change settings, double-click the relationship, then click the Ref. Integrity tab. To create a trigger or stored procedure, choose Database > View > Code Selector, then click New.


P4851 error message
P4851

<type> : Row types, domain types, unnamed row types, and distinct types not based on a built-in data type are not supported in the IBM DB2 DBMS. No DDL will be generated.

Explanation:

IBM DB2 only permits complex types to alias a single built-in data type. No DDL will be generated for the invalid type.

How to fix:

Redefine the type to be based on a single built-in data type. To do so, double-click the type, then click the Aliased Type tab, then select a built-in data type from the list.


P4852 error message
P4852

<type> : Type inheritance is not supported in the IBM DB2 DBMS. No DDL will be generated.

Explanation:

IBM DB2 does not support the ability to define a parent-child relationship between two separate types.

How to fix:

Remove the type inheritance relationship. To do so, click to select it, then press Delete.


P4853 error message
P4853

<column> : %s type columns not based on a built-in type are not supported in the IBM DB2 CREATE TABLE statement.

Explanation:

IBM DB2 only allows columns to be based on a built-in data type, distinct type, or domain type.

How to fix:

Base the offending column on a built-in data type, distinct type, or domain type. To do so, right-click the table, choose Edit Columns, click the Data Type tab, then select a different data type.


P4854 error message
P4854

<column> : Unnamed row type column is not supported in the IBM DB2 CREATE TABLE statement.

Explanation:

IBM DB2 does not support the ability to insert an unnamed row type into a table as a column.

How to fix:

Split the unnamed row type column into separate columns.


LEGEND

PINK	User Interface element that’s linked to the topic immediately below the UI paragraph.
BLACK	Text that exists in Visio. If a topic says “No help topic is associated with this item.” that means that the topic needs to be written. The topic existed in InfoModeler, but was never written.
RED	Art that exists in Visio.
TEAL	Comments from Nanette to Susan, or from Nanette to Nanette.


GENERIC -- dialog box OK button


Accepts any changes you made and closes the dialog box.

To close the dialog box without saving your changes, click Cancel.


GENERIC -- dialog box Cancel button


Closes the dialog box without retaining any changes.


GENERIC -- Wizard Back button


Displays the previous wizard screen.


GENERIC -- Wizard Next button


Displays the next wizard screen.


GENERIC – Wizard Finish button


Closes the wizard and implements the options you selected.


GENERIC -- Wizard Bitmap


Click an option with the Help pointer for details about that option. Or press F1.


Database > Document Options > Help button


Database Document Options

Database > Document Options

Set default options for how your database model diagram will appear on the drawing page. The defaults you set are saved only with the current model diagram.

General	Choose the graphical notation set and name options you want to display.
Table	Choose the columns and table display attributes, primary key order, and data type display, and whether to display IDEF1X optionality.
Relationship	Choose whether to display relationships. If you choose to display them, select whether to represent relationships with Crow’s Foot notation, whether to display cardinality and referential integrity, and how to display the relationship verb phrase and name.
For help about each dialog box option, right-click the option, then choose What’s This.


Database > Document Options > Defaults button


Sets the default settings for the document to the current settings (Set As), or resets the default settings to those last set for the document (Restore) or to the Visio defaults (Restore Original).


Database > Document Options > General tab > IDEF1X


Uses symbols from the IDEF1X data structure specification language.


Database > Document Options > General tab > Relational


Uses common symbols to indicate relational table structures.


Database > Document Options > General tab > Conceptual Names


Displays the conceptual name for a database object as specified in its Properties dialog box.


Database > Document Options > General tab > Physical Names


Displays the physical name for a database object as specified in its Properties dialog box.


Database > Document Options > General tab > Both


Displays the physical and conceptual names for a database object as specified in its Properties dialog box.


Database > Document Options > General tab > Based on Symbol Set


For models that use IDEF1X notation, displays the conceptual name for a database object as specified in its Properties dialog box.

For models that use Relational notation, displays the physical name for a database object as specified in its Properties dialog box.


Database > Document Options > Table tab > Primary Keys


Displays primary keys in the model. Options under Orders specify how the primary keys appear. If unchecked, a column designated as primary key does not appear in the model unless the column has another property that is displayed as specified by the Annotations option.


Database > Document Options > Table tab > Foreign Keys


Displays foreign keys in the model. If unchecked, a column that is a as foreign key does not appear in the model unless the column has another property that is displayed as specified by the Annotations option.


Database > Document Options > Table tab > Alternate Keys


Displays alternate keys in the model for any columns that have a unique index. If unchecked, a column with an alternate key does not appear unless the column has another property that is displayed as specified by the Annotations option.


Database > Document Options > Table tab > Indexes


Displays columns that have an index in the model (but not those with a unique index). If unchecked, a column with an index does not appear unless the column has another property that is displayed as specified by the Annotations option.


Database > Document Options > Table tab > Non Keys


Displays all columns that are not keys in the model. If unchecked, a column that is not a key does not appear unless the column has another property that is displayed as specified by the Annotations option.


Database > Document Options > Table tab > Annotations


Annotates columns in a model by displaying the following column property symbols:

FK	Foreign key
In	Non-unique index
Un	Unique index


Database > Document Options > Table tab > Vertical line(s)

Displays a vertical line in database shapes to separate the column name from annotations and data types that are shown.


Database > Document Options > Table tab > Don't Show


Does not display information about column data types (the default).


Database > Document Options > Table tab > Show Physical


Displays data types in a model based on the current target database.


Database > Document Options > Table tab > Show Portable


Displays the generic data types in a model that are used by Visio Enterprise but not specific to a database platform.


Database > Document Options > Table tab > Primary keys at top


For data models that support the separate display of primary keys, displays the table component keys beginning with the primary keys.


Database > Document Options > Table tab > Draw separator line


For data models that support the separate display of primary keys, displays a horizontal separator between the last primary key component and the first non-primary key column.


Database > Document Options > Table tab > Physical order


Displays the table component keys in the order they appear in the database. The primary key is not separated from other columns.


Database > Document Options > Table tab > Show IDEF1X Optionality '(0)'


Displays the optionality symbol for models using IDEF1X notation.


Database > Document Options > Relationship tab > Show Relationships


Displays relationship shapes in the model. When unchecked, other options in this tab are not available.


Database > Document Options > Relationship tab > Cardinality (IDEF1X)


Displays cardinality notation on relationship shapes.


Database > Document Options > Relationship tab > Referential Integrity


Displays the following symbols on relationship shapes to indicate referential integrity constraints:

u:R	Indicates that when changing values in a primary key column, change all values in other tables that reference that primary key column.
d:R	Indicates that when deleting the primary key, delete all referenced values.


Database > Document Options > Relationship tab > Show Verb Phrase


Displays role text on relationship shapes. By default, a connecting line includes the text that identifies the relationship.


Database > Document Options > Relationship tab > Forward Text


Displays the forward predicate role text on relationship shapes.


 Database > Document Options > Relationship tab > Inverse Text


Displays the inverse predicate role text on relationship shapes.


Database > Document Options > Relationship tab > Show Physical Name


Displays the name of relationships on the shapes’ connecting line based on the name used by the target database.

By default, displays ForeignKeyn, where n is the serial identifier of this relationship.


Database > Document Options > Relationship tab > Don't Display Name


Specifies not to display any text on the relationship shapes’ connecting lines.


Database > Document Options > Relationship tab > Draw with Crow's Feet


Replaces the one-to-many graphical symbol with a crow’s foot notation in the model.


Database > Drivers > Help button


Database Drivers

Database > Drivers

Configures your Visio Enterprise and ODBC drivers. When you configure your database drivers, you specify a default driver and default mapping for column creation, associate a 32-bit ODBC driver with a particular Visio Enterprise driver, and configure default settings such as preferred settings for portable data types.

NOTE For an association between a Visio Enterprise driver and a 32-bit ODBC driver to work properly, the drivers you select must be designed to work with each other. For example, you would associate a Visio Enterprise Sybase driver with a vendor-supplied ODBC Sybase driver.

When you reverse engineer or generate a database, or update a model or database, Visio Enterprise lists the available data sources based on the database driver associations you establish.

For help about each dialog box option, right-click the option, then choose What’s This.


Database > Drivers > Drivers tab > Set As Default


Sets the driver selected under Installed Visio Drivers to be the default for the currently open model diagram. The selected driver name appears in the title bar of the Tables & Views window, Code window, and Types window.


Database > Drivers > Drivers tab > Installed Visio Drivers


Lists all Visio Enterprise database drivers associated with an ODBC driver.


Database > Drivers > Drivers tab > Setup


Displays the Setup dialog box, where you can associate the selected Visio Enterprise driver with a 32-bit ODBC driver.


Database > Drivers > Default Mapping tab > Default Category Type for Column Creation


Establishes the default settings that appear on the Data Type tab of the Column Properties dialog box for the current model.


Database > Drivers > Default Mapping tab > Category

NOTE TO ME: I know this sets the default settings that are used in another dialog; I just can’t remember which dialog. Should specify.--nje


Selects a category type and changes the options under Type so that you can define the default category type used in the current model.


Database > Drivers > Default Mapping tab > Type

NOTE TO ME: I know this sets the default settings that are used in another dialog; I just can’t remember which dialog. Should specify.--nje


Establishes default settings that appear in the appropriate Properties dialog boxes in the current model.


Database > Drivers > Default Mapping tab > Size


Establishes the default size settings that appear in the appropriate Properties dialog boxes in the current model.


Database > Drivers > Default Mapping tab > Length


Establishes the default length settings that appear in the appropriate Properties dialog boxes in the current model.


Database > Drivers > Default Mapping tab > Scale


Establishes the default scale settings that appear in the appropriate Properties dialog boxes in the current model.


Database > Drivers > Driver Misc tab > Generate comments in the script file


Adds comments from Visio Enterprise to the DDL script generated by the Update Database or Generate Wizard.


Database > Drivers > Driver Misc tab > Generate only for those with user-specified notes


Add comments to the DDL script generated by the Update Database or Generate Wizard from the text of the Notes tabs on the Properties dialog boxes.


Database > Drivers > Driver Misc tab > Generate from the user-specified notes and auto-generate notes when unspecified


Adds comments to the DDL script generated by the Update Database or Generate Wizard from the text of the Notes tabs on the Properties dialog boxes and from Visio Enterprise.


Database > Generate > Shift+F1


Generate Wizard

Database > Generate

Provides options for generating a DDL script with instructions for generating a database based on your model, or for connecting to a database and generating the contents of your model.

The Generate Wizard creates a database schema for a specific DBMS by gathering the information from the database model, checking the model for errors, checking the model’s semantics for compliance with DBMS-specific requirements, and mapping the validated model to an optimally normalized database schema.

For help about each option, right-click the option, then choose What’s This.


Database > Generate > Step 1 > Generate a Text File with the DDL Script

Database > Update > Step 1 > Generate a Text File with the DDL Script


Specifies to generate a text file that contains all DBMS-specific code (usually SQL) necessary to create a physical representation of your database model. After the wizard creates the script, you must manually run it from within your database application.


Database > Generate > Step 1 > File Name

Database > Update > Step 1 > File Name


Sets the filename and path of the DDL script created by the wizard. Click [image] to open the Save As dialog box.


Database > Generate > Step 1 > Generate New Database


Specifies to connect to your target database and generate a database schema based on the contents of your model. This option is available only if your server supports creation of a database through 32-bit ODBC drivers.


Database > Generate > Step 1 > Remember the generated database state


Stores an image of the generated database internally that is used for comparison when you update a model (Database > Update). This option is most useful when databases, such as Microsoft Access, add implied indexes and you want to incorporate them into the model. After the database has been generated, the extra schema objects are added to the model.

Clear this checkbox clear to prevent Visio® Enterprise from storing an image of the generated database. The next time you use the Update Database Wizard, the model appears to Visio Enterprise as if it had never been generated into a database.


Database > Generate > Step 2 > Installed Visio Drivers

Database > Update > Step 2 > Installed Visio Drivers

Database > Update > Step 3 > list box

Database > Reverse Engineer > Step 1 > Installed Visio Drivers

Database > Model > Update > Step 1 > Installed Visio Drivers


Lists all Visio Enterprise database drivers associated with an ODBC driver.


Database > Generate > Step 2 > Setup

Database > Update > Step 2 > Setup

Database > Reverse Engineer > Step 1 > Setup

Database > Model > Update > Step 1 > Setup


Displays the Setup dialog box, where you can associate the selected Visio Enterprise driver with a 32-bit ODBC driver.


Database > Generate > Step 2 > Created <type> File


Specifies to generate a new database. The name of this option changes depending on the drivers you have selected. If a driver does not support direct creation of a new database, this option is dimmed.


Database > Generate > Step 2 > <type> File Already Exists


Specifies to update an existing database. The name of this option changes depending on the drivers you have selected.


Database > Generate > Step 2 > Data Source Name


Specifies the name of the new data source to be established on your system when you are creating a new database. A data source name resides on your system, but can apply to databases on other devices.


Database > Generate > Step 2 > New


Displays the Create A New Data Source dialog box, where you can define a new data source.


Database > Generate > Step 2 > "…" button


Displays the Browse For Folder dialog box, so that you can locate the path information that will appear in the Name box.


Database > Generate > Step 2 > File Name/Directory Name/Database Name


Names the new file, database, directory, or schema.


Database > Generate > Step 2 > Installed Visio Drivers > Microsoft SQL Server > Extract Server Information


Lists devices on the server which you can select and specify a size for. The wizard then adds this information to the CREATE DATABASE statement it generates.

If disabled, the new database is created on the default device with the default size.


Database > Generate > Step 3 > list box

Database > Update > Step 5 > list box


Displays the proposed additions and updates.


Database > Generate > Step 4 > Warnings list box

Database > Update > Step 6 > list box


Displays potential conflicts. See the Output window for additional warnings.


Database > Modeling Preferences > Help button


Modeling Preferences

Database > Modeling Preferences

Establishes the default settings used by Visio Enterprise for all database modeling sessions until new defaults are set.

For help about each dialog box option, right-click the option, then choose What’s This.


Database > Modeling Preferences > Logical Diagram tab > Always drop from model


Specifies to remove a deleted table from the model as well as its visual representation (that is, the particular Entity shape) on the drawing page.


Database > Modeling Preferences > Logical Diagram tab > Drop from model only if last occurrence on diagram


Specifies to removes a deleted table from the model only if no other representation of the table exists, either in the Tables & Views window or on the drawing page.


Database > Modeling Preferences > Logical Diagram tab > Never drop from model


Specifies that deleting a table removes only its visual representation on the drawing page (that is, the particular Entity shape). An instance of the table remains in the Tables & Views window.


Database > Modeling Preferences > Logical Diagram tab > Ask user what to do


Specifies to display a message box whenever an Entity shape is deleted from the model asking whether to remove only the shape (but retain an instance of the table in the Tables & Views window), or remove the shape and the table it represents from the model.


Database > Modeling Preferences > Logical Diagram tab > Show relationships after adding table to diagram


Displays relationships for a new instance of a table that you add to the drawing page.


Database > Modeling Preferences > Logical Diagram tab > Show relationships after adding type to diagram


Displays relationships for a new instance of a type that you add to the drawing page.


Database > Modeling Preferences > Logical Diagram tab > Sync conceptual and physical names in new tables and columns when typing


For new tables you create, specifies to synchronize the conceptual and physical names when you change either one or the other in a model.


Database > Modeling Preferences > Logical Misc tab > Propagate on Add


Creates a foreign key relationship when you connect a non-identifying relationship line between two tables. Visio Enterprise creates a new column in the child table and identifies a foreign key relationship between the two tables.

If disabled, the parent-to-child relationship is created, but the model will not be semantically valid until you modify the relationship to associate the parent with a child column. Then you can create a foreign key relationship with a column of a different name from that of the parent.


Database > Modeling Preferences > Logical Misc tab > Propagate on Delete


Specifies to delete any foreign key column(s) from a child table if the defined foreign key relationship is deleted from the model.

If disabled, only the relationship is dropped, and any columns specified as foreign key are left in their parent table.


Database > Modeling Preferences > Logical Misc tab > Name Conflict


Specifies behavior when adding a foreign key, and a table of the same name already exists in the child table.


Database > Modeling Preferences > Logical Misc tab > Entity


Specifies the prefix that is used to form the default conceptual name that appears on the Definition tab of the Table Properties box.


Database > Modeling Preferences > Logical Misc tab > Attribute


Specifies the prefix that used to form the default conceptual name that appears on the Definition tab of the Column Properties box.


Database > Modeling Preferences > Logical Misc tab > Table


Specifies the prefix that is used to form the default physical name that appears on the Definition tab of the Table Properties box.


Database > Modeling Preferences > Logical Misc tab > Column


Specifies the prefix that is used to form the default physical name that appears on the Definition tab of the Column Properties box.


Database > Modeling Preferences > Logical Misc tab > Type


Specifies the prefix that is used to form the default name that appears on the Definition tab of the Type Properties box.


Database > Modeling Preferences > Logical Misc tab > Field


Specifies the prefix that is used to form the default physical name that appears on the Definition tab of the Field Properties box.


 Database > Modeling Preferences > Logical Misc tab > Default Name Suffixes > Primary Key


No help topic is associated with this item.


Database > Modeling Preferences > Logical Misc tab > Default Name Suffixes > Foreign Key


No help topic is associated with this item.


Database > Modeling Preferences > Logical Misc tab > Default Name Suffixes > Alternate Key


No help topic is associated with this item.


Database > Modeling Preferences > Logical Misc tab > Default Name Suffixes > Index Fields


No help topic is associated with this item.


Database > Modeling Preferences > Logical Misc tab > FK Name Generation Option


No help topic is associated with this item.


Database > Report > Shift+F1


Report Wizard

Database > Report

Creates customizable reports in Visio® Enterprise that describe your database model by displaying data definitions and formatting information. For example, you can create a report that documents your database design to present to a client.

You can create reports that summarize file and database statistics or that document the tables in your model. In addition, if you are creating an object relational model, you can also report on data types.


Database > Report > Step 1 > Start with this page in the future


Displays this starting page when you choose Database > Report.

If disabled, displays the next screen (Step 2 of 3) when you start the wizard.


Database > Report > Step 2 > Choose the type of report you wish to create


Lists available report types for the model.


Database > Report > Step 2 > Description


Describes the selected report’s contents.


Database > Report > Step 3 > list box


Summarizes your choices in the wizard. If this information is not correct, click Back or Cancel.


Database > Report > Finish > Preferences tab > Relational


Uses Relational terminology, such as “table” and “column” in your report.


Database > Report > Finish > Preferences tab > IDEF1X


Uses IDEF1X terminology, such as “entity” and “attribute” in your report.


SUSAN: On the Preferences tab, there are several other options for which help is already defined (Conceptual, Physical, Show Annotations, Default To <report design>), but the topics don’t seem to be here, and I can’t find them in the original report.rtf file.

NANETTE: 9/29/98 I don’t see ANY of these options when I go into this dialog. (I’m running TR18.) On the Preferences tab, I only see: Relational, IDEF1X, Include External Tables. How do you get these other options to appear?


Database > Report > Finish > Attributes tab > Select All


Selects all items in the list to add to the report.


 Database > Report > Finish > Attributes tab > Deselect All


Cancels the selection of all items in this list.


Database > Report > Finish > Attributes tab > Default


Selects the default attributes to add to the report.


 Database > Report > Finish > Sort/Group tab > Available Sort Keys


Lists report objects by which a report can be organized.

Choose one primary object by which to sort this report, then any other keys to resolve divisions within the primary object group.

Double-click a report object in this list to add it to the list of sort keys.


 Database > Report > Finish > Sort/Group tab > ">>" button


Adds the selected item to the Selected Sort Keys list.


 Database > Report > Finish > Sort/Group tab > "<<" button


Removes the selected sort key from use in ordering this report.


 Database > Report > Finish > Sort/Group tab > Selected Sort Keys


Lists in order the report objects that will be used to sort the report contents.

Click [image] or [image] to change list order.


 Database > Report > Finish > Sort/Group tab > Group Sorted Records By


Specifies a sort key by which divisions can be made within the report.

By default, report divisions, such as pages, are made only as needed. You can choose to divide the report into sections based on any of the sort keys that have been used to make the report.


 Database > Report > Finish > Sort/Group tab > Default button


Restores the list of sort keys (and possible values) to the default state.


Database > Report > Finish > Headers tab > Report Title


Specifies the title of your report. Type any text into this window or insert a formatting code by using the Insert button.


Database > Report > Finish > Headers tab > Document Title


Specifies a subtitle for the report. Type any text into this window or insert a formatting code by using the Insert button.


Database > Report > Finish > Headers tab > Group Header


Specifies a group header based on the Group Sorted Records By option on the Sort/Group tab. Type any text into this window or insert a formatting code by using the Insert button.


Database > Report > Finish > Headers tab > Sample Report field


Previews the headers as they will appear in the final report.


Database > Report > Finish > Headers tab > Default button


Restores the text in the Report Title, Document Title, and Group Header boxes to the default values.


Database > Report > Finish > Headers tab > Insert button


Inserts a formatting code at the current cursor insertion point.


 Database > Report > Finish > Pagination tab > Document Separator


Specifies the formatting to use in separating sections of the report.


 Database > Report > Finish > Pagination tab > Continuous


Specifies to number the report pages consecutively from front to back.

If disabled, starts the numbering with 1 for each new source document in a report based on multiple source documents.


 Database > Report > Finish > Pagination tab > Restart at Starting Page Number


Starts the page numbering with 1 for each new source document in a report based on multiple source documents.

If disabled, numbers the report pages consecutively from front to back.


 Database > Report > Finish > Pagination tab > Group Separator


Specifies the formatting to use in separating groups in the report. Set the groups you want on the Sort/Group tab.


 Database > Report > Finish > Pagination tab > Record Separator


Specifies the formatting to use in separating records in the report. All the information about one table or entity, or object type, is considered a record.


 Database > Report > Finish > Pagination tab > Starting Page Number


Sets the starting page number for the report.


 Database > Report > Finish > Pagination tab > Page Setup


Opens the Page Setup dialog box, where you can change various printed page characteristics.


Database > Report > Finish > Pagination tab > Page Setup > Help button


Database > Report > Finish > Print > Copies


Copies

Enter the number of copies of each document you want.

Choose Collate to keep all pages of each copy in consecutive order.


Database > Report > Finish > Print > Collate Copies


Collate Copies

To organize pages when you print multiple copies of a document, select the Collate Copies check box. A complete copy of the document is printed before the first page of the next copy is printed.


Database > Report > Finish > Print > All


Print all pages in the document.

You can print just the current page, or you can print a range of pages.


Database > Report > Finish > Print > Current Page


Print only the page that is active.


Database > Report > Finish > Print > Pages


Print a range of pages in the document.

You can specify a series of consecutive pages, or you can specify multiple series and single pages together.

Series	3–10
Mixture	1, 3–6, 8, 11


Database > Report > Finish > Print > Print to File


Direct print output to a file, instead of to a printer.

Specify a name for the output file.

This file contains all the printer codes that your print stream would normally contain. To print the file, use the Copy command.


Database > Report > Finish > Print > Browse


Click to find the location where you can store the file you are going to create.

Do this before you specify a file name. Clicking this button clears any value in the prompt.


Database > Report > Finish > Print > Setup


Click to change printer configuration.

You can change the designated printer and some aspects of page formatting, including paper size.


Database > Report > Finish > Print > Help


Printing Visio Enterprise documents

Each kind of Visio® Enterprise document can be printed.

For multiple copies of multiple page documents, you can collate the pages, or print all copies of each page, one at a time.


Page Setup dialog box

Report Preview window, Pagination tab, click Page Setup

Sets various printed page characteristics for the report you want to print, such as paper orientation, printer margins, and headers and footers.

For help about each dialog box option, right-click the option, then choose What’s This.


Database > Report > Finish > Pagination tab > Page Setup > Margins tab > Apply To


Specifies the extent of the report for which these changes apply.

You can restrict the formatting changes to a single page, or have it apply to the entire report.


Database > Report > Finish > Pagination tab > Page Setup > Margins tab > Top


Distance from the top edge of the paper to the first printed material, including header data.

Laser printers do not print to the edge of a page.


 Database > Report > Finish > Pagination tab > Page Setup > Margins tab > Bottom


Specifies the distance from the bottom edge of the paper to the first printed material. This includes footer data.

Laser printers do not print to the edge of a page.


 Database > Report > Finish > Pagination tab > Page Setup > Margins tab > Left


Specifies the distance from the left edge of the paper to the first printed material.

Laser printers do not print to the edge of a page.


 Database > Report > Finish > Pagination tab > Page Setup > Margins tab > Right


Specifies the distance from the right edge of the paper to the last printed material on the right edge of the page.

Laser printers do not print to the edge of a page.


 Database > Report > Finish > Pagination tab > Page Setup > Margins tab > Units of measure


Specifies the units used for margin settings.


 Database > Report > Finish > Pagination tab > Page Setup > Margins tab > Draw Border


Specifies to print a border around the body of the report, exclusive of any header and footer information.


 Database > Report > Finish > Pagination tab > Page Setup > Header/Footer tab > Select a region to edit by clicking on the preview window


Changes the options for headers and footers on this tab.

You can also click an area of the Preview page to display different header and footer options.


 Database > Report > Finish > Pagination tab > Page Setup > Header/Footer tab > Left Header


Specifies the text that appears in the specified region.

You can use plain text or a Visio® Enterprise formatting code.


 Database > Report > Finish > Pagination tab > Page Setup > Header/Footer tab > After macro expansion


Displays the expanded version of the formatting code specified in the edit box.


 Database > Report > Finish > Pagination tab > Page Setup > Header/Footer tab > Set


Sets the font for the selected header or footer segment.

This font applies only to the selected design element.


 Database > Report > Finish > Pagination tab > Page Setup > Size/Type tab > Paper Size


Sets the printer paper size for the report.


 Database > Report > Finish > Pagination tab > Page Setup > Size/Type tab > Width


Displays the paper width for the selected paper size option.


 Database > Report > Finish > Pagination tab > Page Setup > Size/Type tab > Height


Displays the paper height for the selected paper size option.


 Database > Report > Finish > Pagination tab > Page Setup > Size/Type tab > Portrait


Uses vertical paper orientation.


 Database > Report > Finish > Pagination tab > Page Setup > Size/Type tab > Landscape

Uses horizontal paper orientation.


 Database > Report > Finish > Pagination tab > Page Setup > Size/Type tab > Set as Default Size


Uses the current settings as the default.


Database > Reverse Engineer > Shift+F1


Reverse Engineer Wizard

Database > Reverse Engineer

Steps you through the process of connecting to the target database management system (DBMS) that you want to reverse engineer.

To create a connection, you can use the wizard to specify an installed Visio Enterprise driver and the 32-bit ODBC (Open Database Connectivity) data source. However, for best results, set your default driver to the target database you want to reverse engineer before running the wizard.

The information that the wizard can extract depends upon the capabilities of the DBMS. If your DBMS makes some of the schema definition available, Visio Enterprise makes those options available in the Reverse Engineer Wizard.

For help about each wizard option, right-click the option, then choose What’s This.


Database > Update > Shift+F1


Update Database Wizard

Database > Update

Steps you through the process of connecting to a database, comparing the model in Visio Enterprise to the target database, and then resolving any differences by updating the model or the database.

To update the database, you can choose to generate a DDL script that performs the changes or directly alter the database.

For help about each wizard option, right-click the option, then choose What’s This.


Database > Model > Check > Shift+F1


Check Model Wizard

Database > Model > Check

No help topic is associated with this item.


Database > Model > Update > Shift+F1


Update Model Wizard

Database > Model > Update

Steps you through the process of connecting Visio Enterprise to your target database, comparing the model diagram to the actual database’s schema, and then resolving any conflicts.

If the wizard detects differences between the model and database, you can choose to either update the model, or ignore the conflict for now.

For help about each wizard option, right-click the option, then choose What’s This.


Database > Reverse Engineer > Step 1 > Next > Data Source

Database > Update > Step 2 > Next > Data Source

Database > Model > Update > Step 1 > Next > Data Source


Lists the available data sources based on the database driver associations you establish.

To modify the configuration for a driver, select the driver, then click Setup.


Database > Reverse Engineer > Step 1 > Next > User

Database > Update > Step 2 > Next > User

Database > Model > Update > Step 1 > Next > User


Specifies the user name to log into a host or server database system.


Database > Reverse Engineer > Step 1 > Next > Password

Database > Update > Step 2 > Next > Password

Database > Model > Update > Step 1 > Next > Password


Specifies the password to log into a host or server database system.


Database > Reverse Engineer > Step 2 > Primary Keys


Specifies to extract primary keys from the target database.


Database > Reverse Engineer > Step 2 > Indexes


Specifies to extract indexes from the target database.


Database > Reverse Engineer > Step 2 > Foreign Keys


Specifies to extract foreign keys from the target database.


Database > Reverse Engineer > Step 2 > Triggers


Specifies to extract triggers, including trigger code, from the target database.


Database > Reverse Engineer > Step 2 > Stored Procedures


Specifies to extract stored procedures, including procedure code, from the target database.


Database > Reverse Engineer > Step 3 > Select the tables…

Database > Reverse Engineer > Step 4 > Tables list


Displays all the tables that you can extract from the target database.


Database > Reverse Engineer > Step 3 > Select All


Selects all the tables in the list.


Database > Reverse Engineer > Step 3 > Deselect All


Cancels the selection of all tables that have been selected in the list.


Database > Reverse Engineer > Step 4 > Catalog Info list


Displays all database structures that you have selected to be reverse engineered.


Database > Update > Step 1 > Detect Changes in the Database


Specifies to synchronize the current model with a database.


Database > Update > Step 1 > Log Conflicts


Creates a text file that logs all conflicts between the model and database discovered by the wizard.


Database > Update > Step 1 > Update the Database


Specifies to incorporate into the target database all the changes that your model reflects in its current structure.


Database > Update > Step 2 > Data Sources

Database > Reverse Engineer > Step 1 > Data Sources

Database > Model > Update > Step 1 > Data Sources


Lists the available data sources based on the database driver associations you establish.

To modify the configuration for a driver, select the driver, then click Setup.


Database > Update > Step 2 > New

Database > Reverse Engineer > Step 1 > New

Database > Model > Update > Step 1 > New


Displays the Create A New Data Source dialog box, where you can define a new data source.


Database > Update > Step 3 > Resolution

Database > Model > Update > Step 2 > list box


Displays all conflicts between your model and the database whose structure it represents. To resolve a conflict, select it in the list, then choose an option: No Change, Update Model, or Update Database.


Database > Update > Step 4 > list box

Database > Model > Update > Step 3 > list box


Lists the changes that will be made to your model to synchronize it with the target database.

You can expand the branches of the tree to see details.


Database > User Defined Types > Shift+F1


User Defined Types

Database > User Defined Types

Specifies to add, remove, and edit custom data types. When you work with portable data types, you can use the default specifications or define a user-defined data type for easy reuse.

User-defined data types can save time and ensure consistency by providing a reusable data type with a standard definition.

For example, you can create user-defined types that match in name those of your DBMS. You can then use data type names in Visio Enterprise that correspond to those of your target DBMS.

Another use is to create data types that are subsets of broader categories.

You can copy definitions from existing user-defined data types to new ones.

NOTE Before you set data type information in your database model, you should be familiar with the data types and storage requirements supported by your target DBMS. Refer to the documentation for your target DBMS to determine which data type to assign.

For help about each dialog box option, right-click the option, then choose What’s This.


Database > User Defined Types > User-Defined Types

Database > User Defined Types > Add > list


Lists existing user-defined data types.


Database > User Defined Types > Description


Type text in this box to describe the user-defined data type.


Database > User Defined Types > Category


Lists portable data types available in Visio® Enterprise.


Database > User Defined Types > Type


For the selected category, lists applicable attributes.

Some values for Type also require Size, Length, or Scale values.


Database > User Defined Types > Size


For the selected category and type, specifies size.


Database > User Defined Types > Precision


Specifies the number of integers used to express a value.


Database > User Defined Types > Scale


Specifies the number of digits to the right of the decimal point.


Database > User Defined Types > Add


Creates a new user-defined type with a default name and type definition.

You must name the new data type, and you must match it to the native portable data type used by Visio® Enterprise.


Database > User Defined Types > Add > Data Type Name


Enter a unique name for the new data type.


Database > User Defined Types > Add > Copy From


Copies the definition of the user-defined data type selected in the list.


Database > User Defined Types > Remove


Deletes the selected user-defined type. If the type has been assigned to an object, a message appears asking whether to delete the user-defined type.


Database > User Defined Types > Rename


Opens the Rename User-Defined Type dialog box.


Database > User Defined Types > Rename > New Name


Enter a new name for the user-defined type.


Right-click Category > Table Inheritance Properties > Help button


Table Inheritance Properties

Right-click Category shape, choose Table Inheritance Properties

Defines a category’s discriminator attribute on a parent table. Using a category establishes a foreign key relationship from the parent table to the child tables connected to the Category shape.

Category tables are subtypes of a parent table. For example, an employee’s record (the generic parent) might contain a job-type column (the category discriminator); category entities in this example might include engineer, technician, and administrator.

If a category table contains all possible subtypes, it is considered complete; if it contains only some possible subtypes it is considered incomplete.

By default, an attribute is not selected as the category discriminator. You must choose an attribute, or the model will fail to validate when you build it.

For help about each option on this tab, right-click the option, then choose What’s This.


PLACEHOLDER: If you open Table Inheritance dialog for a Table Inheritance shape that isn’t connected, you get a help message about “Nothing is selected…” I can’t find this topic.

NANETTE: I couldn’t figure out how to do this…Can you show me, and then I’ll track this down?


Right-click Category > Table Inheritance Properties > Definition tab > None


Sets an available attribute as the category discriminator. By default, when a category is created, it does not have an attribute assigned to it as the category discriminator.


Right-click Category > Table Inheritance Properties > Definition tab > Category is Complete


If checked, indicates that the category (a subtype of its parent) is considered one of a finite set of children, all of which are represented in this model.

If you know that some branch of the parent leads to a child that you are not including in this model, do not check this box.


Right-click Entity > Edit Columns > Edit > Help button


Column Properties For <Name>, Definition tab

Right-click Entity shape, choose Edit Columns, click Edit

Specifies attributes for a column in a table.

In addition to naming properties, you can determine whether null values are allowed for the selected column.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Entity > Edit Columns > Edit > Definition tab > Physical Name


Identifies the name of the column as it appears in its table.

You can change the column name to be more descriptive.

For example, a table can have two columns with the names Money and Money1. The reference mode of the shared object type is money. You can change the column name to better reflect its function—Wholesale or Retail, for example.


Right-click Entity > Edit Columns > Edit > Definition tab > Conceptual Name


Identifies a name used for a column in the conceptual view of the model.


Right-click Entity > Edit Columns > Edit > Definition tab > Allow NULL Values


Allows NULL values in this column.

If unchecked, any row that has no value for this column will cause validation to fail.


Right-click Entity > Edit Columns > Edit > Definition tab > Sync Names when typing


As you type in the Physical Name or Conceptual Name box, causes the other to be updated with the same name.


Column Properties For <Name>, Datatype tab

Right-click Entity shape, choose Edit Columns, click Edit

Specifies how Visio® Enterprise maps portable data types to platform-specific types used by your target DBMS.

You can display either Portable or Physical Data Types, and assign Data Types to columns.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Portable Data Type


Displays data type choices among the portable data types that Visio® Enterprise uses.

These data types are automatically mapped to corresponding data types in your target DBMS. Choose Display Driver Datatype to see how Visio Enterprise has mapped its portable data type.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Portable Data Type > User Defined Type


Lists all user-defined data types.

To define a new data type, choose Database > User-Defined Data.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Portable Data Type > Category


Lists portable data types available in Visio® Enterprise.

The data type definition you construct here automatically maps to the nearest native data type of your DBMS.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Portable Data Type > Type


For the selected category, lists applicable attributes.

Some values for Type also require Size, Length, or Scale values.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Portable Data Type > Size


For the selected category and type, specifies size.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Portable Data Type > Length


Specifies the number of integers used to express a value.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Portable Data Type > Scale


Specifies the number of digits to the right of the decimal point.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type


Changes the options on the Data Type tab to show how a data type of the target database is mapped to the portable Visio® Enterprise data type.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Installed Visio Drivers


Lists Visio Enterprise database drivers associated with an ODBC driver. The default driver is highlighted for the current portable data type (shown on this tab when Show Portable Data Types is selected).


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Mapped Physical Data Type

SUSAN: I can’t figure out when this popup comes up.—nje

NANETTE: Me neither… I wonder how I got it to display originally? Let’s just ignore this one.


Shows the physical data type (native to the underlying DBMS) to which Visio® Enterprise will map the portable data type specified for the currently selected object type.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Change > Native Type


Shows the physical data type for the target DBMS to which the portable data type is mapped.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Change > Length


For applicable data types, specifies the number of integers used to express the value. The more integers, the finer the precision.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Change > Scale


For applicable data types, specifies the number of digits that appear after the decimal point.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Change > Identity


Identifies that the column contains system-generated values that uniquely identify each row within a table.

You can use this feature to generate sequential numbers (for example, employee IDs). When inserting values into a table with an identity column, the database automatically generates the next identifier based on the last used identity value.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Informix > Change > Precision


For certain data types, indicates the total number of significant digits.

Values range from 1 - 16.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Informix > Change > Scale


Specifies the number of digits to the right of the decimal point.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Informix > Change > Largest Unit


Specifies the highest value in the range that defines the data type.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Informix > Change > Smallest Unit


Specifies the lowest value in the range that defines the data type.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Informix > Change > Fraction Precision


Specifies the number of digits that represent fractions of a second, which implies the degree of precision.

Values range from 1 to 5. The default, 3, represents thousandths of a second.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Informix > Change > From Interval


Specifies the starting value in the range that defines the data type.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Informix > Change > From Interval Precision


No help topic is associated with this item.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Informix > Change > To Interval


Specifies the ending value in the range that defines the data type.


Right-click Entity > Edit Columns > Edit > Data Type tab > Show Physical Data Type > Informix > Change > To Interval Precision


No help topic is associated with this item.


Right-click Entity > Edit Columns > Edit > Collection tab > ? button


Column Properties For <Name>, Collection tab

Right-click Entity shape, choose Edit Columns, click Edit

Specifies whether the column is a single value or contains a collection of information.

Collections may be sets, lists, or multiple values, and may only be used in object-relational models.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Entity > Edit Columns > Edit > Collection tab > Unordered, non-repeating group of values (Set)


Allows population instances of a field in a column to have multiple values, but each value must be unique. The values do not have any sorting criteria on them, therefore they are unordered.


Right-click Entity > Edit Columns > Edit > Collection tab > Ordered group of values (List)


Creates an ordered collection of elements that allows duplicate elements. Each element in the collection has an ordinal position. An ordinal position is a position by which a value can be accessed. Because two values can be the same, they are differentiated by their ordinal positions.


Right-click Entity > Edit Columns > Edit > Collection tab > Unordered, repeating group of values (MultiSet)


Creates a collection of elements that can have duplicate values. The elements do not have ordinal positions.


Right-click Entity > Edit Columns > Edit > Collection tab > Single value (Column)


Specifies that there is no collection type property applied. This is the default type.


Right-click Entity > Edit Columns > Edit > Check tab, press ? button


Column Properties For <Name>, Check tab

Right-click Entity shape, choose Edit Columns, click Edit

Creates check clause code that enforces constraints for a column.

Visio Enterprise automatically generates the check clause code based on a range or set of values that you specify on this tab. You can customize the automatically generated code.

Automatically generated check clause code for a column does not appear in the Code window. If you then generate or update a DDL script for your target database, Visio Enterprise adds the check clause to the Code window for that database.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Entity > Edit Columns > Edit > Check tab > Add button


Adds the specified set or range of values to the Defined Values/Ranges box as a new check clause.


Right-click Entity > Edit Columns > Edit > Check tab > Del button


Deletes the check clause selected in the Defined Values/Ranges list.


Right-click Entity > Edit Columns > Edit > Check tab > From box


Enter the minimum value that defines the required range to check.


Right-click Entity > Edit Columns > Edit > Check tab > Defined Values/Ranges


Lists the specified ranges or values.


Right-click Entity > Edit Columns > Edit > Check tab > To box


Enter the maximum value that defines the required range to check.


Right-click Entity > Edit Columns > Edit > Check tab > Value box

SUSAN: When I click What’s This in the dialog for this box, I get “no topic associated” message. But the following topic should come up… ID mapping problem?--nje


Enter a value to include in a set of values. After each value, click Add.


Right-click Entity > Edit Columns > Edit > Extended tab > Installed Visio Drive

Right-click Entity > Table Properties > Indexes tab > Options > Installed Visio Drivers

Right-click Entity > Table Properties > Extended tab > Installed Visio Drivers


Lists all Visio Enterprise database drivers associated with an ODBC driver.


Right-click Entity > Edit Columns > Edit > Check tab > Show Value/Range


No help topic is associated with this item.


Right-click Entity > Edit Columns > Edit > Check tab > Show Check Clause Code


No help topic is associated with this item.


Right-click Entity > Edit Columns > Edit > Extended tab > Change

Right-click Entity > Table Properties > Indexes tab > Options > Change


If enabled, this button brings up a dialog box in which you can configure index properties specific to the selected database driver.


Right-click Entity > Edit Columns > Edit > Notes tab > Help button


Column Properties For <Name>, Notes tab

Right-click Entity shape, choose Edit Columns, Edit

Enter notes about columns on this tab. The text you enter on this tab appears in reports that you can create by using the Database > Report command.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Entity > Edit Columns > Edit > Notes tab > Notes


Enter notes about columns. The text you enter here appears in reports that you can create.


Right-click Entity > Table Properties > Help button


Table Properties For <Name>, Definition tab

Right-click Entity shape, choose Table Properties

Specifies physical and conceptual names for the table and allows you to choose whether to synchronize the names as you work on this tab.

You can specify a name space value for the table to distinguish it from similarly named tables in the model.

This tab also displays information reported by the host database management system (DBMS) about the database owner and the path of the source database. The Defining Type field is available only when a table is empty, and lists all composite data types so you can create a typed table.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Entity > Table Properties > Definition tab > Physical Name

Right-click View > View Properties > Definition tab > Physical Name


Specifies the name of table as it appears in the physical database.


Right-click Entity > Table Properties > Definition tab > Conceptual Name

Right-click View > View Properties > Definition tab > Conceptual Name


Specifies the name of table as it appears in conceptual modeling.


Right-click Entity > Table Properties > Definition tab > Name Space

Right-click View > View Properties > Definition tab > Name Space


Specifies a value that distinguishes identically named model elements in a source project that contains more than one model.

For example, if another source document has one or more elements with the same name as elements in the current model, and you do not want them to be merged, you can use different values for name space to keep them distinct in the final project.


Right-click Entity > Table Properties > Definition tab > Owner

Right-click View > View Properties > Definition tab > Owner


Specifies read-only information about the selected table’s owner reported by the host database management system during the reverse engineering process.


Right-click Entity > Table Properties > Definition tab > Source Database

Right-click View > View Properties > Definition tab > Source Database


Specifies the database from which the selected table was extracted as reported by the host database management system during the reverse engineering process. The value is read-only.


PLACEHOLDER: Missing option: Defining Type.

<Definition> Lists all composite data types so you can create a typed table. The Defining Type field is available only when a table is empty.


Right-click Entity > Table Properties > Definition tab > Sync Names when typing

Right-click View > View Properties > Definition tab > Sync Names when typing


Specifies to synchronize the conceptual and physical names when you change either one or the other on this tab.


Right-click View > View Properties, SQL tab


No help topic is associated with this item.


Table Properties For <Name>, Primary ID tab

Right-click Entity shape, choose Table Properties

On this tab, you can edit, define, or delete primary keys from a list of available columns and choose whether to create an index on primary keys.

When you first display this tab, you can view any primary key data about the table. You can then use this tab to create or change the constitution of the primary key or its physical name, as well as add an index to the primary key.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Entity > Table Properties > Primary ID tab > Primary ID Columns


Lists columns that are components of the primary key.


Right-click Entity > Table Properties > Primary ID tab > Physical Name


Specifies the name of the primary key as required by the target database.

This is a generic name; for example, PrimaryKey or PrimaryKey3. It is specific to the target database and must comply with its requirements.


Right-click Entity > Table Properties > Primary ID tab > "All >>"


Moves all components of the primary key from the Primary ID Columns list to the Available Columns list.


Right-click Entity > Table Properties > Primary ID tab > "<<"


Moves the selected column from the Available Columns list to the Primary ID Columns list.


Right-click Entity > Table Properties > Primary ID tab > ">>"


Moves the selected component of the primary key from the Primary ID Columns list to the Available Columns list.


Right-click Entity > Table Properties > Primary ID tab > Available Columns


Lists all columns in the current table that you can use to compose the primary key.


Right-click Entity > Table Properties > Primary ID tab > Generate As


No help topic is associated with this item.


Right-click Entity > Table Properties > Primary ID tab > Create Index


Enables an index on the primary key.

Most database systems require an index on each primary key. This is often associated with the physical name of the primary key.


Table Properties For <Name>, Indexes tab

Right-click Entity shape, choose Table Properties

On this tab, you can define an index and edit its properties for the selected table.

For example, you can edit the name of an index, change index options, rearrange the order of columns in an index, or set extended attributes for an index. Extended attributes for an index are driver-specific and are not supported by all DBMSs.

Visio Enterprise automatically creates unique indexes on primary keys.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Entity > Table Properties > Indexes tab > Index Name


Lists existing indexes.


Right-click Entity > Table Properties > Indexes tab > Indexed Columns


Lists columns that are included in the selected index.


Right-click Entity > Table Properties > Indexes tab > "All >>"


Moves all columns from the Indexed Columns list to the Available Columns list.


Right-click Entity > Table Properties > Indexes tab > "<<"


Moves the selected column in the Available Columns list to the Indexed Columns list.


Right-click Entity > Table Properties > Indexes tab > ">>"


Moves the selected columns from the Indexed Columns list to the Available Columns list.


Right-click Entity > Table Properties > Indexes tab > Available Columns


Lists columns that can be included in an index definition.


Right-click Entity > Table Properties > Indexes tab > Rename > Non-unique Index

Right-click Entity > Table Properties > Indexes tab > New > Non-unique Index


Enter a name for this index. The name must be valid for the DBMS that is implementing this database structure.

By default, Visio Enterprise concatenates the table name with the _IDX suffix to form an index name which changes to reflect any changes in the table name.

If you enter a different name, Visio Enterprise does not automatically update it if the table name changes.

To restore the default index name behavior, enter '' (two single quotation marks).


Right-click Entity > Table Properties > Triggers tab > ? button

Right-click Entity > Table Properties > Check tab > ? button

Unfortunately, both of these tabs use the same number, so they have to be in the same help topic. (At this late date, I don’t think we can get Dev to actually change these numbers to be unique.)


Table Properties For <Name>, Triggers and Check tab

Right-click Entity shape, choose Table Properties, and then click the Triggers tab

On this tab, you can add, edit, remove, or preview the code for triggers.

When you reverse engineer a database that contains triggers, or add a new trigger to a table in your model, the trigger code is shown on this tab and is listed under Local Code in the Code window.

Trigger code is included in the DDL (Data Definition Language) script created when you use the Generate or Update Database Wizard.

A trigger can be executed when specific database events occur, such as when a record is inserted, updated, or deleted. For example, you can use a trigger to log audit information to a separate table, calculate derived information such as the extended cost of price times quantity, notify logged-on users of limits that have been exceeded, or call a stored procedure.

Right-click Entity shape, choose Table Properties, and then click the Check tab

On this tab, you can create a check clause to enforce constraints on a table.

When you create a new check clause for a table, the code is specific to the platform currently selected in the Database Drivers dialog box and appears in the Code window for that driver.

You can also create a new check clause by working in the Code window, which lists all check clauses extracted from a database you reverse engineer as local code.

For help about each option on these tabs, right-click the option, then choose What’s This.


Right-click Entity > Table Properties > Triggers > Triggers

Right-click Entity > Table Properties > Check > Check Clauses


No help topic is associated with this item.


Right-click Entity > Table Properties > Triggers > Preview

Right-click Entity > Table Properties > Check > Preview


No help topic is associated with this item.


Right-click Entity > Table Properties > Triggers > Edit

Right-click Entity > Table Properties > Check > Edit


No help topic is associated with this item.


Right-click Entity > Table Properties > Triggers > Add

Right-click Entity > Table Properties > Check > Add


No help topic is associated with this item.


Right-click Entity > Table Properties > Triggers > Remove

Right-click Entity > Table Properties > Check > Remove


No help topic is associated with this item.


PLACEHOLDER: Missing options on Check tab: Check Clauses, Preview, Edit, Add (FYI: Add displays code editor), Remove. All currently display “No help topic associated with this item”


Right-click Entity > Table Properties > Extended tab

Right-click Type > Table Properties > Extended tab

Right-click Entity > Edit Columns > Edit button > Extended tab


Table Properties For <Name>, Extended tab

Right-click Entity shape, choose Table Properties

Sets DBMS-specific extended attributes for use with the Visio Enterprise database drivers.

Extended attributes are specific to a target DBMS, and allow you to control more precisely the way objects defined in your model are mapped to a target database.

For example, with Informix you can use extended attributes to choose dynamic storage options for tables. Similarly, if you are targeting your model to SQL Server 6.5, you can specify the segment of the target database on which a table will be stored.

Extended attributes for an index are driver-specific and are not supported by all DBMSs.

NOTE Unless you are the database administrator or have the equivalent permissions, for best results, do not change the extended attribute settings.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Entity > Edit Columns > Edit > Extended tab > Attributes

Right-click Entity > Table Properties > Indexes tab > Options > list box

Right-click Entity > Table Properties > Extended tab > Attributes

SUSAN: I can’t figure out what you click on the tab to get this. So I can’t figure out how to rephrase… “this utility” doesn’t mean anything. –nje

NANETTE: It won’t come up now, so I say we ignore this one.


List of index attributes that have been modified through this utility.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Data Capture None


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Data Capture Changes


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > In Table Space


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Index In


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Long In


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Not Logged Initially


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > New


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > Delete


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > Properties


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > New > Name


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > New > Regular


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > New > Long


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > New > Temporary


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > New > Overhead


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > New > Transfer Rate


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > New > System


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > New > Database


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > New > Extent Size


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > IBM DB2 > Change > Table Space > New > Using Container


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Online Dynamic Server


Chooses the OnLine Dynamic Server version of Informix database servers.

Visio Enterprise also supports INFORMIX-Universal Server.


Right-click Entity > Table Properties > Extended tab > Informix > Change > SE Database Server


Chooses the INFORMIX-SE version of Informix database servers.

Options in this dialog box do not apply to this system.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Pathname


Identifies the table, as well as operating system path that defines its location.

Do not use a file extension.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Dbspace


Specifies to create all database tables in the area of the computer system designated as dbspace.

For details, refer to your Informix-OnLine Dynamic Server documentation.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Fragment Expression


Specifies to fragment your table storage space, breaking up tables, indexes, and so on, according to an expression-based distribution scheme.

This fragmentation scheme requires knowledge of data distribution. It is the most effective fragmentation scheme, but requires more knowledge of the physical nature of the database system than does the round robin scheme.

For details, refer to your Informix-OnLine Dynamic Server documentation.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Round Robin


Specifies to fragment your table storage space, breaking up tables, indexes, and so on, according to a round robin distribution scheme.

This is the default fragmentation scheme, and performs best for decision support applications.

For details, refer to your Informix-OnLine Dynamic Server documentation.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Fragmented Expression


To specify the FRAGMENT BY EXPRESS clause of the CREATE TABLE statement, enter one or more expressions that determine how this table will be fragmented for distribution.

For example, the following example fragments the table according to the primary key (id_num) value, placing each fragment in a particular dbspace:

id_num > 0 AND id_num <= 20	dbsp1
id_num > 20 AND id_num <= 40	dbsp2
id_num > 40 	dbsp3


Right-click Entity > Table Properties > Extended tab > Informix > Change > First Extent


Specifies the size of the first extent used by the CREATE TABLE statement.

The default is 8K.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Next Extents


Specifies the size of each extent after the first used by the CREATE TABLE statement.

The default is 8K.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Lock Page


Specifies to lock each page that is in memory.

This default locking behavior affects the number of rows that fit in the given page.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Lock Row


Specifies to lock only each row that is being accessed.

This locking behavior enables more rows to be accessed at the same time, but may adversely affect performance.


Right-click Entity > Table Properties > Extended tab > Informix > Change > In Dbspace


Opens the Informix New Dbspace dialog box, where you can create new dbspaces on your system.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Dbspace


Specifies an existing dbspace to use either as the main storage area (when In Dbspace is in effect), or as the space for any fragments that are not specified in fragmented expression (when expression-based fragmentation is in effect).


Right-click Entity > Table Properties > Extended tab > Informix > Change > Add the Rowid Column for Fragmented Table


Specifies to add the unique ROWID system to a fragmented scheme.

By default, Informix does not add a ROWID (row identification) column to tables stored in a distributed scheme (fragmentation schemes).

NOTE For best results, use primary keys to identify rows. The use of ROWID is a substitute for true primary key columns and should be used only when primary keys do not exist.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Dbspace > New Dbspace


Enter the name by which to create a new dbspace value.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Dbspace > Dbspace list box


Lists existing dbspace values on this system.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Dbspace > Add


Adds the value in the New Dbspace box to the Dbspace list.


Right-click Entity > Table Properties > Extended tab > Informix > Change > Dbspace > Remove


Removes the selected dbspace value from the Dbspace list.

This button is available only after you select an item in the list that was created using this dialog box. You cannot remove dbspace values supplied by the Informix system that appear in this list.


Right-click Entity > Table Properties > Extended tab > Change > Available Devices

Right-click Entity > Table Properties > Extended tab > Sybase SQL Server > Change > Available Devices


Lists devices that have been created by the database administrator for the DBMS currently selected.


Right-click Entity > Table Properties > Extended tab > Change > Clustered PK

Right-click Entity > Table Properties > Extended tab > Sybase SQL Server > Change > Clustered PK


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > Change > Segment

Right-click Entity > Table Properties > Extended tab > Sybase SQL Server > Change > Segment


Enter a name for the segment of the host SQL database on which the index or table is to be stored.

The segment will be stored on the selected device in the Available Device list.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Initial Transaction Entries Allocated


Specifies a value from 1 to 255 for the INITRANS parameter that sets the minimum number of concurrent transactions.

Each transaction that modifies a block of data requires an entry in the block.

The default value for an index is 2; for a table it is 1.

NOTE For best results, do not change this value.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Maximum Concurrent Update Transactions Allowed


Specifies a value from 1 to 255 for the MAXTRANS parameter that sets the maximum number of concurrent transactions that update a data block.

This value does not affect the number of queries that can occur.

The default value is operating system-specific.

NOTE For best results, do not change this value.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Percentage of Space to Leave Free for Updates and Insertions


Specifies a value form 1 to 99 for the PCTFREE parameter that sets the percentage of a data block left free for updates and insertions.

The default is 10.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Minimum Percentage of Unused Space ORACLE Maintains for Each Data Block


Specifies a value from 1 to 99 for the PCTUSED parameter that sets the minimum percentage of used space for a data block.

When used space in a data block drops below this figure, the data in the block is subject to transfer to a different block.

The default is 40 and the range is from 1 to 99.

The value of PCTUSED + PCTFREE must be less than 100.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Use Default Tablespace


Uses the tablespace that contains the index.

By default, this is the tablespace of the owner of the schema that contains the index.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Tablespaces


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Constraint


Specifies extended attributes of a primary key constraint.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Storage


Modifies the default characteristics of Oracle index storage.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Constraint > Use Exception Table


Specifies for Oracle to store information about any rows that violate an integrity constraint for the table in Table Name.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Constraint > Table Name


Specifies a name of an existing table to use when Use Exception Table is checked.

The table must already exist, or Oracle cannot provide an exception table.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Constraint > Index Used


Opens the Index Used Attribute dialog box, where you can refine the specification for the index that enforces the primary key constraint.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Storage > First Extent


Specifies a value from 2 to an operating-system specific maximum for the size of the first extent created for any database object.

The default value is 5 data blocks. The size of a data block is specific to the operating system.

You can change the units of measure from data blocks to kilobytes or megabytes.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Storage > Subsequent Extents


Specifies a value from 1 to an operating-system specific maximum for the size of the next extent created for any database object; for example, an index.

The default value is 5 data blocks. The size of a data block is specific to the operating system.

You can change the units of measure from data blocks to kilobytes or megabytes.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Storage > Optimal Size for Rollback Segment (0 for NULL)


Specifies the optimal size of the rollback segment.

The default is NULL, meaning that Oracle does not unallocate rollback segment extents.

When a value is specified, Oracle attempts to maintain that size by unallocating rollback segments as they become free.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Storage > In Kilobytes


Specifies to use kilobytes as the units of measure in the Size boxes.

NOTE Do not use this setting unless you are familiar with the characteristics and requirements of the host operating system.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Storage > In Megabytes


Specifies to use megabytes as the units of measure in the Size boxes.

NOTE Do not change this setting unless you are familiar with the characteristics and requirements of the host operating system.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Storage > In Data Blocks


Specifies to use data blocks as the units of measure in the Size boxes.

The size of a data block is specific to the operating system.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Storage > Extents Allocated When Created


Specifies the number of extents allocated when the index is created.

The default value is 1, which means that Oracle allocates only the initial extent.

A higher value means that more space is allocated for the index than is initially used.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Storage > Maximum Extents Allowed


Specifies the total number of extents (including the first) that Oracle can allocate for the index.

The minimum value is 1, and the maximum value is operating system-specific.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Storage > Percent Increase for Next Growing Extent


Sets the percentage increase in the size of each extent over that of the previous extent.

The default value is 50%. Specify 0 (zero) to keep all extents the same size.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Storage > Number of Freelist Groups


Specifies the number of free list groups for an index.

This value applies only to configurations using the Oracle Parallel Server option in parallel mode.

This is the default and the minimum value is 1.


Right-click Entity > Table Properties > Extended tab > Oracle Server > Change > Storage > Number of Freelists for Each Group


Number of free lists for the free list group that applies to the index.

Oracle recommends that if the number of waits for free blocks exceeds 1% of the total number of index requests, then free lists should be added.

For details, refer to your Oracle documentation.


Right-click Entity > Table Properties > Extended tab > Sybase SQL Anywhere Server > Change > Use Default Root Database File (Default Dbspace)


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > Sybase SQL Anywhere Server > Change > Dbspaces

Right-click Entity > Table Properties > Extended tab > Sybase SQL Anywhere Server > Change > Update > Dbspaces


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > Sybase SQL Anywhere Server > Change > Update


Opens the Update Dbspace dialog box.


Right-click Entity > Table Properties > Extended tab > Sybase SQL Anywhere Server > Change > Update > Dbspace


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > Sybase SQL Anywhere Server > Change > Update > File Name


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > Sybase SQL Anywhere Server > Change > Update > Add


No help topic is associated with this item.


Right-click Entity > Table Properties > Extended tab > Sybase SQL Anywhere Server > Change > Update > Remove


No help topic is associated with this item.


Right-click Entity > Table Properties > Notes tab > ? button


Table Properties For <Name>, Notes tab

Right-click Entity shape, choose Table Properties

Enter notes about tables and their attributes. The text you enter on this tab appears in reports that you can create by using the Database > Report command.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Entity > Table Properties > Notes tab > Notes

Right-click View > View Properties > Notes tab > Notes


Enter notes about tables. The text you enter here appears in reports that you can create.


Right-click Relationship > Relationship Properties > Help button


Relationship Properties For <Name>, Definition tab

Right-click Relationship shape, choose Relationship Properties

On this tab, you can associate columns in the parent and child tables and enter role names for foreign keys.

Relationships indicate visually how the tables in your database model interact with one another, and editing their properties enables you to control how data is stored and retrieved in the database.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Relationship > Relationship Properties > Definition tab > left list box


Lists columns in the parent table.

When you connect a relationship shape between two tables, the begin point of the line is connected to the parent table.


Right-click Relationship > Relationship Properties > Definition tab > <-Associate->


Associates the two columns selected in the parent and child lists, creating a relationship.


Right-click Relationship > Relationship Properties > Definition tab > right list box


Lists columns in the child table.

When you connect a relationship shape between two tables, the endpoint of the line is connected to the child table.


Right-click Relationship > Relationship Properties > Definition tab > Foreign Key Role Name


For IDEF1X models, specifies the role name defined by the foreign key relationship.

You can use this value to clarify the business rule that is reflected in this foreign key relationship.


Relationship Properties for <Name>, Name tab

Right-click Relationship shape, choose Relationship Properties

On this tab, you can define the text that appears in the Verbalizer window to describe the roles performed by the model’s objects.

Role text is read in the direction of parent to child. The verb phrase describes the parent’s role; the inverse phrase describes the child’s role.

You can also specify the physical name of this relationship on this tab, and provide descriptive text.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Relationship > Relationship Properties > Name tab > Verb Phrase


Describes the parent’s role.

Role text appears in the Verbalizer window to clarify the relationship between the two tables. The text is not used to name any database objects.


Right-click Relationship > Relationship Properties > Name tab > Inverse Phrase


Describes the child’s role.

Role text appears in the Verbalizer window to clarify the relationship between the two tables. The text is not used to name any database objects.


Right-click Relationship > Relationship Properties > Name tab > Physical Name


Specifies the name of relationship as it appears in the physical database.

This value is used differently depending on the target DBMS. For many systems, this value is the name of the foreign key constraint, as defined in an SQL ADD CONSTRAINT clause.


Right-click Relationship > Relationship Properties > Name tab > Notes


Enter notes about the relationship.

The text you type appears in the Verbalizer window.


Relationship Properties For <Name>, Misc tab

Right-click Relationship shape, choose Relationship Properties

On this tab, you can choose the type of cardinality, whether the relationship is identifying or non-identifying, and whether the relationship is optional.

TIP To display cardinality settings for a model that uses IDEF1X notation, check Cardinality (IDEF1X) on the Relationship tab of the Database Document Options dialog box.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Relationship > Relationship Properties > Misc tab > Zero or More


For IDEF1X models, specifies that any number of entities, including none at all, can be related as specified.


Right-click Relationship > Relationship Properties > Misc tab > One or More


For IDEF1X models, specifies that at least one instance of an entity will be related as specified.


Right-click Relationship > Relationship Properties > Misc tab > Zero or One

For IDEF1X models, specifies that there can be no more than one instance of the entity in this relationship.


Right-click Relationship > Relationship Properties > Misc tab > Frequency


For IDEF1X models, specifies that no more than the number of entity instances shown in the Min. and Max. boxes can be related as specified.


Right-click Relationship > Relationship Properties > Misc tab > Frequency Min


For IDEF1X models, specifies the minimum number of entity instances that can be related as specified.


Right-click Relationship > Relationship Properties > Misc tab > Frequency Max


For IDEF1X models, specifies the maximum number of entity instances that can be related as specified.


Right-click Relationship > Relationship Properties > Misc tab > Identifying


Specifies an identifying relationship, where the foreign key relationship includes a primary key component in the child table.

Part of the primary key of the child table is also part of the primary key of the parent table.


Right-click Relationship > Relationship Properties > Misc tab > Non-Identifying


Specifies a non-identifying relationship, where the foreign key relationship does not include a primary key component in the child table.

The part of the parent table primary key that is shared by the child table is not part of the child table primary key.


Right-click Relationship > Relationship Properties > Misc tab > Optional


Specifies that NULL values are possible in the connected attribute.

NULL values are only possible if the relationship is non-identifying (not part of a primary key).


Relationship Properties For <Name>, Ref. Integrity tab

Right-click Relationship shape, choose Relationship Properties

Sets options that determine the effect on the child table when information in the parent table is updated or deleted.

In this tab, you can make exceptions to the general referential integrity policies you have set for the database at large. The options you set affect only the selected relationship. Visio Enterprise automatically generates referential integrity constraints between related tables using the settings you define.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Relationship > Relationship Properties > Ref. Integrity tab > On Parent Update > No Action


Specifies to make no automatic changes to the foreign key when the parent in the selected relationship is updated. This is the default.

When you update the model, the target database does not attempt an update that violates the relationship between these two tables.

This type of referential integrity is also called RESTRICTED.


Right-click Relationship > Relationship Properties > Ref. Integrity tab > On Parent Update > Cascade


Specifies to make the same changes to the foreign key as are made to the primary key when the parent in the selected relationship is updated.


Right-click Relationship > Relationship Properties > Ref. Integrity tab > On Parent Update > Set NULL


Specifies to set the entire foreign key to NULL when the parent in the selected relationship is updated.

When an update to the parent table of this relationship changes the value in the parent column, the value of this child column will be set to NULL.

Use this option to prevent a new parent value from applying automatically to all child cases.

This type of referential integrity is also called NULLIFIES.


Right-click Relationship > Relationship Properties > Ref. Integrity tab > On Parent Update > Do Not Enforce


Specifies to disable referential integrity when the parent in the selected relationship is updated.


Right-click Relationship > Relationship Properties > Ref. Integrity tab > On Parent Delete > No Action


Specifies to make no automatic changes to the foreign key when the parent in the selected relationship is deleted. This is the default.

This type of referential integrity is also called RESTRICTED.


Right-click Relationship > Relationship Properties > Ref. Integrity tab > On Parent Delete > Cascade


Specifies to make the same changes to the foreign key as are made to the primary key when the parent in the selected relationship is deleted.


 Right-click Relationship > Relationship Properties > Ref. Integrity tab > On Parent Delete > Set NULL


Specifies to set all foreign key columns in matching rows to NULL when the parent in the selected relationship is deleted.

This type of referential integrity is also called NULLIFIES.


Right-click Relationship > Relationship Properties > Ref. Integrity tab > On Parent Delete > Do Not Enforce


Specifies to disable referential integrity when the parent in the selected relationship is deleted.


Right-click Type > Type Properties > Help button


Type Properties For <Name>, Definition tab

Right-click Type shape, choose Type Properties

You can create named and unnamed row types that act as reusable type definitions for tables or views.

Named row types are based on the SQL3 specification of tables, called typed tables, and are identified within the system as persistent type storage. Unnamed row types are not identified as persistent type storage.

Row types create composite data types that can be used in models that will be implemented on object-relational databases and can be specified as the data type.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Type > Type Properties > Definition tab > Name


Enter a name for the composite type that will appear on the Data Type tab of the Column Properties dialog box and in the Types window.

By default, Visio Enterprise adds a suffix to the name to distinguish its type based on the selection under Composite Type.


Right-click Type > Type Properties > Definition tab > Domain


Domain composite type. Selecting this option enables the Aliased Collection Type option.


Right-click Type > Type Properties > Definition tab > Distinct Type


No help topic is associated with this item.


Right-click Type > Type Properties > Definition tab > Named Row Type


No help topic is associated with this item.


Right-click Type > Type Properties > Definition tab > Aliased Collection Type (visible only if Domain checked)


No help topic is associated with this item.


Right-click Type > Type Properties > Aliased Type Tab > ? button


Type Properties For <Name>, Aliased Type tab

Right-click Type shape, choose Type Properties

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Type > Type Properties > Aliased Type tab > Named Type


Specifies a named row type and enables the list of Visio Enterprise types.


Right-click Type > Type Properties > Aliased Type tab > Named Type > Char > Length

Right-click Type > Type Properties > Aliased Type tab > Named Type > Currency > Precision

Right-click Type > Type Properties > Aliased Type tab > Named Type > Float > Length


Specifies the number of integers used to express a value.


Right-click Type > Type Properties > Aliased Type tab > Named Type > Currency > Scale

Right-click Type > Type Properties > Aliased Type tab > Named Type > Float > Scale

Right-click Type > Type Properties > Aliased Type tab > Named Type > Numeric > Scale


Specifies the number of digits to the right of the decimal point.


Right-click Type > Type Properties > Aliased Type tab > Named Type > list box


No help topic is associated with this item.


Right-click Type > Type Properties > Aliased Type tab > Unnamed Type


No help topic is associated with this item.


Right-click Type > Type Properties > Notes Tab > ? button


Type Properties For <Name>, Notes tab

Right-click Type shape, choose Type Properties

Enter notes about named and unnamed row types. The text you enter on this tab appears in reports that you can create by using the Database > Report command.

For help about each option on this tab, right-click the option, then choose What’s This.


Right-click Type > Type Properties > Notes tab > Notes


Enter notes about types. The text you enter here appears in reports that you can create.


Database > View > Code Selector


Code Selector

Database > View > Code Selector

No help topic is associated with this item.


Database > View > Table Selector


Table Selector

Database > View > Table Selector

No help topic is associated with this item.


Database > View > Type Selector


Type Selector

Database > View > Type Selector

No help topic is associated with this item.


Database > View > Output


Output

Database > View > Output

No help topic is associated with this item.


Database > View > Verbalizer


Verbalizer

Database > View > Verbalizer

Expresses in natural language the meaning of any selected object.

To print the contents of the Verbalizer window, right-click in the window, then click the print button.


Database > Code > Synchronize > Shift+F1


Synchronize

Database > Code > Synchronize

If you’ve created a mirror file of your code, you can keep it in sync with your model by using this command. Then if you edit the code outside of Visio Enterprise, or change it while working in the Code Editor, the changes are synchronized between the model and the mirror file.

Choose Update Mirror File(s) Now to change the code stored in the mirror file to match the model.

Choose Update Model Now to change the code stored in the model to match the mirror file.


Database > Code > Synchronize > Differences, Code column, File column, Type column, DBMS column


No help topic is associated with this item.


Database > Code > Synchronize > Update Mirror File


No help topic is associated with this item.


Database > Code > Synchronize > Update Model Now


No help topic is associated with this item.


Database > Code > Synchronize > Refresh


No help topic is associated with this item.


Database > Code > Synchronize > Select All


No help topic is associated with this item.


Database > Code > Transfer > Shift+F1


Transfer

Database > Code > Transfer

Enables a model to support multiple database platforms by transferring code from one platform to another.

You can use this command to move your code, or a copy of it, from one platform to another. As you work in your model, you can switch between platform-specific versions of the code by changing the default driver for the model.

The Code window provides access to only the version of code for the currently selected database driver. You can create as many platform-specific copies of your code as you need.


Database > Code > Transfer > Move


No help topic is associated with this item.


Database > Code > Transfer > Copy


No help topic is associated with this item.


Database > Code > Transfer > Source DBMS


No help topic is associated with this item.


Database > Code > Transfer > Destination DBMS


No help topic is associated with this item.


Import ERwin ERX Model

Import/Export > Import ERwin ERX Model

Imports ERwin 2.x .erx files and converts them to an IDEF1X data model diagram (.vsd).

The .erx format file is exported by ERwin and contains information about a data model in text form.

Visio Enterprise draws the entities, attributes, relationships, categories, and text blocks in a model diagram. Other objects are converted as follows:

•	ERwin subject areas are converted to pages in the model diagram.

•	ERwin domains are converted to portable data types when Visio Enterprise has a database driver equivalent to an ERwin target server.

If Visio Enterprise does not have an equivalent database driver, a warning message appears and Visio Enterprise maps the ERwin data type to a default data type instead.

NOTE Visio Enterprise does not import the following ERwin features: stored procedures, custom trigger code, or ERwin displays.


Export ERwin ERX Model

Import/Export > Export ERwin Model


Import Visio Database Diagram

Import/Export > Import Visio Database Diagram

Imports diagrams (.vsd files) created by using the Crow’s Foot ERD template or the ERD template in Visio Professional 5.0b.


Comment for previous topic:<I think 5.0c files don’t work; verify, and if true, make a note or let Tech Support deal with it?--nje>


Import VisioModeler IMD Model

Import/Export > Import VisioModeler IMD Model

Imports VisioModeler 1.5, 2.0, 3.0, and 3.1 dictionary model (.imd) files.

Visio Enterprise creates a new model document, recreates each page of the VisioModeler file, and lays out the diagram. All the characteristics of the object types, predicates, and constraints in the model are preserved.