Copyright: Paradox Error Message Help
Citation: Copyright © 1985, 1995 Borland International.


Paradox for Windows Error

No additional information is available on this message.If you see forward and backward browse buttons in the message box, Paradox has a stack of messages there, explaining more about the problem.

If you do not see any browse buttons in the message box, there are no additional messages.

To find out more,

Choose the forward browse button in the message box.

To go back to a previous message,

Choose the backward browse button.


Could not find language driver

The language driver file for the table you are attempting to access cannot be found. This message may also occur when the language driver entry is missing from the system registry or the language file cannot be located.

Solution

Run the Paradox Setup program and reinstall the Borland Database Engine. This will install the language driver as well as enter the correct entries into the system registry.


Corrupt table/index header

This message appears when accessing a table whose header or structure information is damaged. The damage may be to the data file (.DB or .DBF), the index file (.PX, .X??,.Y??, .MDX) or the memo file (.MB, .DBT).

This also may appear if a non Paradox table is renamed to a .db extension, or a non dBASE table is renamed to a .dbf extension.

Solution

If working with Paradox .db tables, run the Table Repair utility (Tools|Table Repair) to correct the damaged file.


Corrupt Memo / BLOB file

This message appears when accessing a table whose memo or BLOBdata is damaged. The memo data is stored in a .MB extension file for Paradox tables or a .DBT extension file for dBASE tables.

Solution

If working with Paradox .db tables, run Table Repair utility (Tools|Table Repair) to correct the damaged file.


Corrupt or missing .VAL file

The .VAL file is missing or damaged.  This message most often occurs in connection with referential integrity. Various table properties are stored in the .VAL file, including referential integrity relationships. If the .VAL file is missing, these relationships cannot be resolved and therefore, this message is displayed.

Solution

Restructure the table and recreate the referential integrity relationship. Since referential integrity information is stored in the master table's .VAL file as well as the detail table's .VAL file, it may be necessary to delete both (from the Windows Explorer or a DOS Prompt window)  to be able to restructure the file.

Note:	VAL files also store other information about the table such as table lookup information, data validation parameters, etc. You should only delete the .VAL file if you know this information about the table so that you can later recreate it.


Corrupt file - other than header

A table is corrupted. If you are attempting to open a form or report, a table associated with the form or report is damaged.

Solution

If the table is a Paradox table, run the Table Repair utility (Tools|Table Repair).


Key violation

The table already contains data which is the same for those field(s) you designated as the table’s key field(s). Records which duplicate the information across all the key fields is not permitted and will result in this message.

Solution

You may choose from the following:

Change the value entered so that there is no duplicate data.

Restructure the table and modify the key. In order to do so, you must first resolve the key violation condition by modifying the data you are trying to save so that it does not duplicate data already entered, or Edit|Undo the current record.


Master record missing

This message occurs when referential integrity is defined between two tables, and you attempt to post a record in a detail table whose field(s) defined in the referential integrity rule is not matched in the master table.

Sometimes occurs as "Master record not found."

Solution

Referential integrity requires that a match must exist in the master table before a detail record can be saved. Therefore, you will not be able to save the current record until the corresponding record in the master table has been entered. Edit|Undo will undo the changes to the detail record and allow you to continue working. You may choose to either,

Modify (or remove) the referential integrity relationship

Add the data to the master file.


Master has detail records. Cannot delete or modify

This message occurs under the following situations:

You are attempting to delete or modify a record however this table is the master table in a referential integrity relationship and corresponding detail records exist.

You are modifying existing data in fields that are defined as part of the referential integrity relationship and the Update Rule is set to “Prohibit”.

Solution

In order to delete a master record, you must delete the individual detail records before the master record can be deleted.

When Update Rule is set to "Prohibit" , changes to existing data in those fields is blocked.

Note:	If you feel this restriction is not necessary for your application, you may choose to modify the structure of the table and remove the referential integrity relationship or remove the Prohibit setting on the Update Rule.


Lookup Table Open operation failed

You are attempting to open a table which has Table Lookup relationships established with other tables. One or more of these other tables could not be opened.

Solution

There are several reasons why this message may occur, including the following common causes,

The table(s) may already be open or otherwise in use. Check for any open documents that have the table in the data model and any ObjectPAL applications that may have the detail table open. If the table is located on a shared drive, another user may have the table open.

The tables may have been renamed outside of Paradox (for example, in the Windows Explorer or a DOS window) and therefore Paradox cannot find the file reference(s). Rename the files back to the original name temporarily to complete the current operation.

Note:	A safer way to rename tables (and the entire family of files that can be associated with any one table) is to select the Rename feature from the right-click menu of the Project Viewer or from the Tools|Utilites menu.


Detail Table Open operation failed

This message occurs while trying to access a table through another table, form or query. This occurs when a table associated with the current table in a referential integrity relationship cannot be opened.

Depending on the operation you are attempting, the detail table may not be available. For example, when restructuring the master table of a referential integrity relationship, an exclusive lock is placed on the detail table as well as the master table. If the detail table is open, the exclusive lock will fail and result in this message.

Solution

Verify that the table is not already open or otherwise in use. Check for any open documents that have the table in the data model and any ObjectPAL applications that may have the detail table open.

If the problem persists:

It is possible that the .VAL file has become corrupted. If you suspect this, you may delete the referential integrity using the Restructure Table dialog box. If you are unable to do this, use the Windows Explorer or DOS to delete the .VAL file for that table and for the other tables (detail or master) involved in the referential integrity.

Then use the Restructure Table dialog box to restore the referential integrity link, as well as any other table properties that were defined before.

Note:	This may require the deletion of several .VAL files depending on the inter-relationships of the tables and other information stored in the .VAL file such as picture formatting, data validation, etc. will be lost. Delete the .VAL file only if the information contained in the .VAL file is known so that it can be recreated.


Invalid parameter

This message occurs while attempting to run a form or report that contains an invalid link between the tables in the data model.The most common cause of this is a change in the file structure of either the master or detail table which causes the link to no longer be valid.

Solution

To correct the invalid link between the two tables, you can choose to either,

Open the form or report in a design window and click the Data Model button. Choose the detail table, then choose the Link button. Create a valid link based on the current file structure.

Use the Restructure Table dialog box to return the file structure of the master and / or detail tables back to the it was when the report or form was created.


Table does not exist

This message can occur when Paradox does not find a specified table.

Solution

There are several reasons why the specified table cannot be found, including the following common causes,

Misspellings of the file name including drive and path reference.

The alias name (if specified) may be valid but is not where the table is stored. If no alias was specified, the default is :WORK: which is the Paradox current working directory. The current working directory may not be where the file is located.

The table may have been renamed. If so, change the reference to the new name or rename the table back.

If using SQL files that reference table names containing punctuation or spaces, enclose the table name in double quotes, for example, "customer data.db".


Directory is controlled by other .NET file

Another user is currently accessing Paradox tables in the same network directory, but with a different Network Control File location.

Solution

All users who access Paradox tables in a particular shared location must have the same net control file directory. This dialog displays the location of the Paradox lock file (PDOXUSRS.LCK) as well as the directory of the Net Control File. To open the table successfully, you must set your Net Control File to the location indicated in the dialog.

To set your Net Control File directory,

1.	Close Paradox and run the BDE Configuration utility.

2.	In the Driver Name list, choose Paradox.

3.	Choose NET DIR. Enter the location for the net control file. Save the new setting and exit the BDE Configuration utility.

4.	Start Paradox. Paradox is now set to the new network control file directory location.

Note:	From within Paradox, you can choose Edit|Preferences and click the tab for the BDE page to see what the current setting for the Network Control File Directory is.


Not initialized for accessing network files

This message occurs when attempting to open a Paradox table located on a network drive when a network control file directory location has not been specified. Paradox requires this setting in order to track file and record lock information.

Solution

To access Paradox tables stored on a network drive, you must specify a location where Paradox can create a network control file. To set your network control file directory,

1.	Close Paradox and run the BDE Configuration utility.

2.	In the Driver Name list, choose Paradox.

3.	Choose NET DIR and enter a location on a shared drive where Paradox should create the network control file. (Check with your network administrator if there's a standard location.) Save the new setting and exit the BDE Configuration utility.

4.	Start Paradox. Paradox is now set to the new network control file directory location.

Note:	From within Paradox, you can choose Edit|Preferences and click the tab for the BDE page to see what the current setting for the Network Control File Directory is.


One or more query rows do not contribute to the ANSWER

This message occurs when a query contains several rows where one or more rows does not contain any checked fields.

Solution

If you have specified several conditions on multiple rows, and have not joined these rows using example elements, you have composed an OR query. You must checkmark the same fields in each row of of an OR query.


Missing comma

This message usually indicates a syntax error in an expression used in the query, or the defined expression is too complex for the query engine to handle.

Solution

Make sure that all expressions used in the query are formatted correctly. Check items such as,

Mathematical signs appear between all values in calculations.

Commas separate multiple selection conditions, for example, >10, <20 and so on.

Commas separate multiple join example elements, for example, Join1, Join2, and so on.

Verify that example elements are properly displayed (they appear in red on a color monitor).

If the condition persists:

Break down the query into two or more separate queries.


Field not found in table

This message occurs when running a query that is based on a table whose file structure has been modified since the query was last saved.

Solution

To correct this situation, choose one of the following:

Recreate the query with the current file structure.

Open the .QBE file in a text editor and remove all references to the field(s) that are no longer in the table.


Expecting consistent number of columns in all rows of table

This message can occur when running a query that has an incorrect number of pipe (|) symbols in the query definition. Often a pipe symbol is missing at the beginning of the field definition, between fields or at the end of the field definition when creating a query string from ObjectPAL or editing a saved query.

Solution

Verify that all pipe symbols are present.

In the following example, note that the final pipe symbol is missing after the "check":

var

   myQBE     Query

endvar

myQBE = Query

   Customber.db   | Customer No |

                  | check

EndQuery

if not myQBE.executeQBE() then

   errorShow()

endif


Older version (see context)

This message occurs when attempting to open a table with a table level higher than the current version of Paradox. For example, you are given a table of Table Type Paradox 7 and attempt to open it in Paradox for Windows 5.0. This can also occur when opening a report or form in Paradox for Windows 4.5, which is based on a Paradox for Windows 5.0-type table.

Solution

In order to open and use the table, you must install a more recent version of Paradox.


Expecting a column separator in table header

This message can occur under the following situations:

When running a query that has an incorrect number of pipe (|) symbols in the query definition.

When attempting to run or open a query file which was created in dBASE.

Solution

You have the following options:

If the query string was created in ObjectPAL, verify that the number of pipe symbols (|) is correct. Often a pipe symbol is missing at the beginning of the field definition, between fields or at the end of the field definition when creating a query string from ObjectPAL.

If the .QBE query file was created in dBASE, this file cannot be interpreted by Paradox and needs to be recreated in Paradox.

Note:	Both dBASE and Paradox save query files to a .QBE file extension so if your original query needs to be run in dBASE, name the newly created query in Paradox to a different name.)


Query string is empty

This message occurs when executing a query containing a tilde variable, where the tilde variable has not been assigned a value.

Solution

Initialize the tilde variable prior to initializing the query variable.

In the example below, cust_no is not assigned a value prior to the initialization of the query variable and will generate the "Query string is empty" error.

var

  myQBE      Query

  cust_no    SmallInt

endvar

myQBE = Query

   customer.db   |  Customer No     |

                 |  Check ~cust_no  |

endQuery

if not myQBE.executeQBE() then

   errorShow()

endif


Cannot activate OLE server

This message occurs when trying to start an OLE server from Paradox.

Solution

The OLE link and activation information is stored in the system registry. Paradox accesses this information in order to launch the specified OLE server.

If you are familiar with the system registry, you may view the various entries that pertain to the OLE server you are attempting to launch, and edit them as necessary. A common scenario has the user moving the location where an application is stored. The application still runs fine but the Windows registry entries are still pointing to the previous location and are no longer found there.

If you are not familiar with the system registry, check the documentation for that application to see whether its registration can be done after installation. If not, reinstall the OLE server application. The information in the registration database is complex and should be set up by the OLE server's installation program.


Cannot modify this table

This message can occur when editing information in a form from a detail table which is set to Read Only.

Solution

In a multi table form with a one-to-one relationship, the detail table is set to Read-Only by default. To allow updates to this table, this property must be turned off. To do so,

1.	Open the form in design mode.

2.	Click the data model button on the toolbar to open the Data Model dialog box.

3.	Right-click the detail table and choose the Read Only property to remove the check mark.

4.	Choose OK to close the Data Model dialog.

5.	Save the form if desired.


Character(s) not supported by Table Language

One or more characters you have entered are not part of the character set available for the language driver of the table and strict translation is set.

Solution

Decide whether it is important to preserve this and similar characters in your table exactly as you have entered them. Based on that decision, you have these alternatives:

If the characters should be stored in the table exactly as entered, then a different language driver must be selected which does support the desired characters. See About Table Language Drivers for more information on language drivers. See To Change Table Language Drivers for steps to change your table's language driver.

You may set strict translation off. By doing so, Paradox will translate a character which is not in the character set of the table's language driver to its nearest equivalent. In most cases, this means that an accented alphabetic letter will be converted to a non-accented equivalent.


A page break cannot cross an object

This message occurs when attempting to place a page break in a report.

Solution

The Breakable property must be checked in the band in which you would like the page break to occur (they are set independently in each band). To set the Breakable property,

1.	Open the report in a design window.

2.	Right-click on the background area of the band in which you'd like to place a page break and select Properties.

3.	Click the tab for the Run Time page.

4.	Place a check mark beside the Breakable property.


Cannot build quick form or report on PASSTHRU SQL

This message appears when attempting to create a quick form or a quick report on the answer table of a SQL statement, when the alias on the SQL statement was specified in the Select Alias dialog.

Solution

Include the alias name within the SQL statement.

For more information on pass-through SQL, see Using pass-through SQL


This record is already locked by another module in this session

This message occurs when you try to lock the same record more than once in the same session of Paradox.

Solution

Check for the source of the original lock and release it. This situation most commonly occurs when multiple forms, scripts, tables, etc. which are based on the same table(s) are open simultaneously. Also, ObjectPAL code in a form or script may have the table open and locked without being obvious.


Invalid alias

This message occurs when attempting to open a file with a specified alias but the alias is not defined.

Solution

Choose Tools|Alias Manager to see all the aliases defined in your current BDE configuration file. Based on the aliases you see in the Alias Manager dialog box, you may notice,

The alias name has been misspelled.

The alias name does not exist. You can add this alias in the Alias Manager dialog box and save the new alias.


The source file does not exist

This message can occur when attempting a Tools|Utilities operation (add, copy, delete, empty, rename, sort or subtract) and specifying a file which cannot be found.

Solution

There are several reasons why the specified table cannot be found, including the following common causes,

Misspellings of the file name including drive and path reference.

The alias name (if specified) may be valid but is not where the table is stored. If no alias was specified, the default is :WORK: which is the Paradox current working directory. The current working directory may not be where the file is located.


Character(s) not supported by Table Language

One or more characters you have entered are not part of the character set available for the language driver of the table and strict translation is set.

Solution

Decide whether it is important to preserve this and similar characters in your table exactly as you have entered them. Based on that decision, you have these alternatives:

If the characters should be stored in the table exactly as entered, then a different language driver must be selected which does support the desired characters. See About Table Language Drivers for more information on language drivers. See To Change Table Language Drivers for steps to change your table's language driver.

You may set strict translation off. By doing so, Paradox will translate a character which is not in the character set of the table's language driver to its nearest equivalent. In most cases, this means that an accented alphabetic letter will be converted to a non-accented equivalent.


Cannot perform this operation with table open

This message occurs when a delete operation is attempted on a table which is currently open.

Solution

Close any objects which may be accessing the table. For example, check the Window menu for the open table and if found, close it. Also check for other document types such as forms, reports and queries that are based on the data in this table. ObjectPAL code may also be accessing this table and keeping it in use.


BLOB, defined
BLOB

Binary large object. Field types that can contain BLOBs include binary, memo, formatted memo, graphic, and OLE. Certain rules apply to these fields as a whole, and they are sometimes discussed collectively as BLOB fields.