Skip to content

Miscellaneous Error Messages

See Also: Finding Specific Errors

Overview

Miscellaneous errors are some errors not stored in a database table but are instead embedded in the runtime or hard-coded into the DataFlex packages (Class Library).

Error List

900 - Filename already exists

Cause

The table is listed in filelist.cfg multiple times.

Resolution

Remove all duplicate table entries for this table until only one remains in filelist.cfg.

999 - Extended Field not defined in DD

Cause

  1. Improper use of a text or binary DataFlex database field in the program code.

Attempt to access a text or binary field with the messages Get/Set Current_Field_Value, Get/Set File_Field_Current_Value, or Get Field_Changed_Value. Since these field types are not supported in all cases, this is an error.

  1. Attempting to access a text field via a DataDictionary without defining it as an extended field.

Resolution

  1. Review the code and make the required corrections.

Also, review the information regarding Field Options.

  1. Define the extended field in the DataDictionary using DefineExtendedField or DefineAllExtendedFields.

999 - Invalid use of overlap with DD

Improper use of an overlap DataFlex database field in the program code.

Overlap fields are available for building relationships and nothing else. Do not directly access overlap fields with DDO messages. It is expected to use the underlying (primary) fields that make up the overlap. In particular:

  • Do not access overlaps with the messages Field_Current_Value, File_Field_Current_Value, or Field_Changed_Value.
  • Never mark any overlap fields as a key field. It does not work. Instead, mark each underlying field as a key field. A key field can consist of multiple fields.
  • Do not use overlap fields with field options, validation tables, entry, exit, or validation messages. Use the underlying fields instead.

Resolution

In most cases, the problem can be fixed by loading the Data Dictionary Builder, removing the DD field settings from the overlap field, and adding the field setting to the underlying fields.

Also, review the information regarding Field Options.

999 – Value must be one of

Additional information presented in the error dialog:

  • File: - a token to be replaced with the file number of the database table triggering the error
  • Field: - a token to be replaced with the table name of the database table triggering the error
  • xx, yy, and zz - tokens representing a list of valid entries for this window

Cause

This error is triggered by failure to enter or select a valid choice of data for the data window for the specific database table field. The list of choices is specified by a Simple Validation list in the DataDictionary for the database table.

Resolution

Enter data that is on the valid list of choices listed.