Page 6-36
Programming
INTER-TEL
®
AXXESS
®
MANUAL VERSION 11.0 – May 2008
Enumerations
• Invalid column <table name>:<column name>: This is only a warning. It indicates
that it was looking for a column, but could not find it in the database. This can happen
if a new column is added in a later version of a major release. If the test is being run on
the older version, this warning will appear. For example, if Column A was added in ver-
sion 5.111, running this test on databases previous to version 5.111 will produce a warn-
ing that Column A could not be found.
• <table name>/<column name> contains an invalid enumeration value [<invalid
value>]: The table has an incorrect value in the indicated column. This corruption is
repaired by changing the field to a correct value. The Repair Status will be Value Set to
<value> where <value> is the field’s new contents.
Enumerations
6.17 Each enumeration field has a set of values that are valid. An error is detected if the field
has a value that is out of this range.
6.18 Possible Error Messages:
• Invalid table <table name>: This is only a warning. It indicates that it was looking for
a table named, but could not find it in the database. This can happen if a new table is
added in a later version of a major release. If the test is being run on the older version,
this warning will appear. For example, if Table A was added in version 5.111, running
this test on databases previous to version 5.111 will produce a warning that Table A
could not be found.
• Invalid column <table name>:<column name>: This is only a warning. It indicates
that it was looking for a column named, but could not find it in the database. This can
happen if a new column is added in a later version of a major release. If the test is being
run on the older version, this warning will appear. For example, if Column A was added
in version 5.111, running this test on databases previous to version 5.111 will produce a
warning that Column A could not be found.
• <table name>/<column name> contains an invalid enumeration value [<invalid
value>]: The table has an incorrect value in the indicated column. This corruption is
repaired by changing the field to a correct value. The Repair Status will be Value Set to
<value> where <value> is the field’s new contents.
Extension Conflicts
6.19 This test checks for extension conflicts.
6.20 Possible Error Messages:
• Found blank extension, device type <device type
>: In this case, a device was found
with a blank extension. The extension is changed to P#XXX where XXX can be from
000 to 999. The Repair Status will be Set to Extension <new extension>.
• Found conflict with extension <extension number>, device types <device type 1>,
<device type 2>: Two devices have the same extension number, and the two device
types are not compatible. This corruption is repaired by changing the extension number
of the second device <device type 2> to P#XXX where XXX can be from 000 to 999.
The Repair Status will be Set to Extension <new extension>.
NOTE: Only 1000 extension conflicts can be cleaned up at a time because there are only
1000 possible extensions in P#XXX to change them to. Therefore, starting at the 1001 exten-
sion, the Repair Status will be Not Repaired. After an extension is set to P#XXX, you can go into
DB Programming and change the extension to a valid number.
To Next Page
Loading...
