Copyright: Corel PARADOX (TM) Error Message Help
Citation: Copyright (c) 1997 Corel Corporation


Paradox for Windows Error
Corel Paradox for Windows Error

No additional information is available on this message. If you see forward and backward browse buttons in the message box, Corel Paradox has additional messages that explain 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

•	Click the forward browse button in the message box.

To go back to a previous message

•	Click the backward browse button.


Could not find language driver

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

Solution

Run the Corel 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 you try to access 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 Corel Paradox table is renamed to a .DB extension, or a non dBASE table is renamed to a .DBF extension.

Solution

If working with Corel Paradox .DB tables, click Tools, Table Repair to run the Tagle Repair utility and correct the damaged file.


Corrupt Memo / BLOB file

This message appears when you try to access a table whose memo or BLOB data is damaged. The memo data is stored in a .MB extension file for Corel Paradox tables or a .DBT extension file for dBASE tables.

Solution

If working with Corel Paradox .DB tables, click Tools, Table Repair to run the Table Repair utility and 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, therefore, this message is displayed.

Solution

Restructure the table and recreate the referential integrity relationship. Because 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 files to be able to restructure the file.

 Note

•	VAL files also contain other information about the table such as table lookup information, data validation parameters, etc. Delete the .VAL file only if you know have a record of this information about the table so that you can recreate it.


Corrupt file - other than header

A table is corrupted. This message is displayed if you are attempting to open a form or report and a table associated with the form or report is damaged.

Solution

If the table is a Corel Paradox table, click Tools, Table Repair to run the Table Repair utility .


Key violation

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

Solution

•	Do one of 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 click Edit, Undo to undo the last action on 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. click Edit, Undo to undo the changes to the detail record and allow you to continue working.

Do one of the following:

•	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

•	To delete a master record, you must first delete the individual detail records.

•	When Update Rule is set to Prohibit, the data in those fields cannot be changed.

 Note

•	If this restriction is not necessary for your application, you can modify the structure of the table and remove the referential integrity relationship or disable the Prohibit setting on the Update Rule.


Lookup Table Open operation failed

You are attempting to open a table that has Table Lookup relationships established with other tables, and 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 Corel Paradox (for example, in the Windows Explorer) and, therefore, Corel Paradox cannot find the file reference(s). Rename the file(s) with 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 click Tools, Utilites, Rename.


Detail Table Open operation failed

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

Depending on the operation, the detail table may not be available. For example, when you restructure 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 fails and this message is displayed.

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, the .VAL file may be corrupted. If you suspect this, you may remove 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

•	Removing referential integrity 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 you have a record of the information contained in the .VAL file so that you can recreate it.


Invalid parameter

This message occurs when you attempt 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 that invalidates the link.

Solution

To correct the invalid link between the two tables, open the form or report in a design window and click the Data Model button. Choose the detail table and click the Link button. Create a valid link based on the current file structure.


Table does not exist

This message occurs when Corel Paradox does not find a specified table.

Solution

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

•	misspelled file name, including drive and path reference.

•	The alias name (if specified) may be valid but does not point to where the table is stored. If no alias was specified, the default is :WORK: which is the Corel 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.

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


Directory is controlled by other .NET file

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

Solution

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

To set your Network Control File directory

1.	Close Corel Paradox and run the BDE Administrator.

2.	In the Driver Name list, choose Corel Paradox.

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

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

 Note

•	From within Corel Paradox, you can click Tools, Settings, Preferences and click the tab for the BDE page to view the current setting for the Network Control File Directory.


Not initialized for accessing network files

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

Solution

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

1.	Close Corel Paradox and run the BDE Administrator.

2.	In the Driver Name list, choose Corel Paradox.

3.	Choose NET DIR and enter a location on a shared drive where Corel 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 Administrator.

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

 Note

•	From within Corel Paradox, click Tools, Settings, Preferences and click the tab for the BDE page to view the current setting for the Network Control File Directory.


One or more query rows do not contribute to the ANSWER

This message occurs when a query contains several rows  but 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 check the same fields in each row of an OR query.


Missing comma

This message 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 error condition persists, break down the query into two or more separate queries.


Field not found in table

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

Solution

Do 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 you run 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 you create a query string from ObjectPAL or when you edit 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 you attempt to open a table with a table level higher than the version of Corel Paradox you are using. This message also occurs when you attempt to open a form or report that uses a higher level table. For example, you are given a table of Table Type Corel Paradox 7 and attempt to open it in Corel Paradox 5.0.

Solution

•	To open and use the table, form, or report, install a more recent version of Corel Paradox.


Expecting a column separator in table header

This message can occur under the following situations:

•	when you run a query that has an incorrect number of pipe symbols (|) in the query definition.

•	when you attempt to run or open a query file that 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 from the beginning of the field definition, between fields, or at the end of the field definition when you create a query string using ObjectPAL.

•	If the .QBE query file was created in dBASE, Corel Paradox cannot interpret the file.

 Note

•	Both dBASE and Corel Paradox save query files to a .QBE file extension. To run your original query in dBASE, name the newly created query in Corel Paradox to a different name.


Query string is empty

This message occurs when you execute a query containing a tilde variable, but 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 you try to start an OLE server from Corel Paradox.

Solution

The OLE link and activation information is stored in the system registry. Corel Paradox accesses this information 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. For example, if you move an application to a new location, the application still runs, but the Windows registry entries point to the previous location.

If you are not familiar with the system registry, check the documentation for the 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 you edit information in a form from a detail table that is set to Read Only.

Solution

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

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 disable the Read Only check box.

4.	Click 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 you must select a language driver that supports the desired characters. For more infomation, see About table language drivers. For information about how to change a language driver, see Changing table language drivers.

•	You can set strict translation off. Corel Paradox will then translate a character that 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 character will be converted to a non-accented equivalent.


A page break cannot cross an object

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

Solution

The Breakable property must be enabled 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 click Properties.

3.	Click the Run Time tab.

4.	Enable the Breakable check box.


Cannot build quick form or report on PASSTHRU SQL

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

Solution

Set the SQL file alias to ":WORK:" and 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 Corel Paradox.

Solution

Check for the source of the original lock and release it. This situation most commonly occurs when multiple forms, scripts, tables, etc. that 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 it being obvious.


Invalid alias

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

Solution

Click 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 following:

•	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.

For more information about aliases, see About aliases.


The source file does not exist

This message can occur when you attempt to run a Utility operation (add, copy, delete, empty, rename, sort or subtract) and specify a file that cannot be found.

Solution

The specified table may not be found for the following reasons:

•	misspelled file name, including the drive and path reference

•	The alias name (if specified) may be valid but it is not where the table is stored. If no alias was specified, the default is :WORK: which is the Corel 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. For more information see About table language drivers and Changing table language drivers.

•	You can set strict translation off. Corel Paradox will then translate a character that 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 you attempt a delete operation on an open table.

Solution

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


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.


alias, defined
Alias

A name you assign to a database in addition to its original name. When you use an alias, you don't need to specify the directory path.


Number is out of range for the given type

You have entered or edited data in a table or form, and one or more of the following conditions are true:

•	more than 15 digits are entered in a Corel Paradox Number field

•	more than 15 digits are entered in a Corel Paradox BCD field

•	a number not within the range of -32,767 to 32,767 is entered in a Short Integer field

•	a number not within the range of -2147483648 to 2147483647 is entered in a Long Integer field

Solution

Enter a valid value for the field type.

To view valid values for the data types for the following table types, click the appropriate topic below.

•	Corel Paradox field types and sizes

•	dBASE field types and sizes

•	Interbase field types and sizes

•	Informix field types and sizes

•	Oracle field types and sizes

•	Sybase field types and sizes

 Note

•	To enter more than 15 digits in a Corel Paradox Number field, use scientific notation, for example, 1e15.


Minimum validity check failed

The value you have entered for a field falls below the Minimum Value specified in the Table Restructure or Structure Information dialog boxes.

Solution

Enter a value that meets the Minimum Value as specified in the Table Restructure or Structure Information dialog boxes. To see the Minimum Value set for fields in the table, click Tools, Utilities, Info Structure. If you have the table currently open in a Table window, use the Info Structure command.

 Note

•	You can also change the value defined in the validity check.


Maximum validity check failed

The value you have entered for a field exceeds the Maximum Value specified in the Table Restructure or Structure Information dialog boxes.

Solution

Enter a value that meets the Maximum Value as specified in the Table Restructure or Structure Information dialog boxes. To see the Maximum Value set for fields in a table, click Tools, Utilities, Info Structure.

 Note

•	You can also change the value defined in the validity check.


Field value required

You have left a field blank (not entered data for a field) whose property is set to Required Field. A Required Field must have a value for that field in each record in the table.

Solution

Enter a value for the field or remove the Required Field setting. To remove the Required Field setting, open the Table Restructure dialog box and click the field in the Field Roster. Disable the Required Field check box to remove this setting.


AS must be followed by the name for the field in the ANSWER table

One of the following situations has occurred:

•	The AS clause is included in a query definition without the name of the field that holds the calculated value.

•	The AS clause is placed in the incorrect order in the query expression. For example, the following expression in a query definition will cause this message to display:

CALC newField AS aNum*100

where aNum is an example element for a number field in the table and newField is a new field in the answer table that contains the result of the expression.

Solution

1.	Add the name of the new field for the calculated value.

2.	Correct the order of expression as follows:

CALC aNum*100 AS newField


Master table level is incorrect

You have set referential integrity rules, however, the table level of the master table must be Corel Paradox 4 or later. Referential integrity is not supported in tables earlier than Corel Paradox 4.

Solution

Set the level of the master table to Corel Paradox 4 or higher. To do this, choose one of the following methods:

•	Click Tools, Table Repair. Specify the table name and set the table level to Corel Paradox 4 or later.

•	Restructure the table and add a field type that was added in Corel Paradox 4 level tables. The field types added in Corel Paradox 4 are: Memo, Formatted Memo, Binary, Graphic and OLE.

You must change the table level (and save this change) before the referential integrity rule can be saved.


A primary index is required when maintained indexes or referential integrity are used

You have attempted to define Referential Integrity rules or a maintained index on a table that does not have a primary key. These features require a primary key on the table.

Solution

Create a primary key.


The primary key can include only the first 16 fields

You have attempted to include more than 16 fields in the primary key of a Corel Paradox table. The maximum number of fields that can be included in a primary key is 16.

Solution

Include a maximum of 16 fields in the primary key.


The index was not named

You did not enter a name for the index on the Save Index As dialog box. You chose Cancel or OK with a blank name field. Names for indexes are required when prompted.

Solution

Enter a name for the index.


Example element has no defining occurrence

You have used an example element in a query definition without assigning it a value.

Solution

Define the example element. Position the cursor under the field you want in the query definition, press F5, then type in the name of the example element you want to define.


Master Table Open operation failed

You are attempting an operation that requires use of the current table and any tables that depend on it. One or more tables that are related to the current table cannot be opened.

Solution

Corel Paradox often opens other tables behind the scenes, based on relationships you have defined in the table’s structure. Examples of such relationships are table lookups and referential integrity.

Check the following conditions and make corrections as applicable:

•	The dependent tables exist in the location they were when the referential integrity rules were defined.

•	The dependent tables were not renamed.

•	The dependent tables are not currently being used exclusively.


Master table is open

You are attempting to restructure a table that is a detail to another table, and that other table (the master table) is already open. Restructuring requires exclusive use of the current table and all the tables to which it is related.

Solution

Corel Paradox often opens other tables behind the scenes based on relationships you have defined in the table’s structure. Examples of such relationships are table lookups and referential integrity.

Close all tables which are referenced in the current table’s structure. To see the table structure information, click Tools, Utilities, Info Structure or open the table and click View, Table Structure.

Tables may also be open if you have a form, report, or query open that uses data from those tables. Close all such documents.


Detail table(s) exist

You are attempting a delete or rename operation on a table that is defined as the master table of a referential integrity rule.

Solution

Restructure the detail table indicated in this message and remove the referential integrity rule that links the two tables.


Master has detail records. Cannot empty it

You are attempting to empty a table which is defined as the master table in a referential integrity rule. Dependent table(s) contain records that require one or more of the existing master table records therefore, you cannot empty all records from the master table.

Solution

Choose one of the following solutions that best fits your needs:

•	If you want to delete master records, delete individual records from the master table.

•	If you do not want to enforce the referential integrity rule, you can restructure the table to remove this dependency.


Self referencing referential integrity must be entered one at a time with no other changes to the table
Self referencing referential integrity must be entered one at a time, with no other changes to the table

Corel Paradox allows you to define a referential integrity relationship where a single table is both the master and the detail table of the relationship. This is self-referencing referential integrity.

Solution

If you define a self-referencing referential integrity rule during a restructure operation, you cannot make other structure changes at the same time. Instead, create the self-referencing referential integrity rule and save the changes. Then restructure the table again and make the other file structure changes that you want in a separate restructure operation.

For more information, see Self-referential integrity.


Detail table is open

You are attempting to restructure a table that is a master to another table, and that other table (the detail table) is already open. Restructuring requires exclusive use of the current table and all the tables to which it is related.

Solution

Corel Paradox often opens other tables behind the scenes. based on relationships you have defined in the table’s structure. Examples of such relationships are table lookups and referential integrity.

Close all tables that are referenced in the current table’s structure. To see the table structure information, click Tools, Utilities, Info Structure or open the table and click View, Table Structure.

Tables may also be open if you have a form, report, or query open that uses data from those tables. Close all such documents.


Cannot make this master a detail of another table if its details are not empty

This message occurs when you set referential integrity between two tables, one of which also has a referential integrity rule set with another table.

Solution

Corel Paradox permits this, however, both referential integrity links should be defined before any data is entered.


Couldn't perform the edit because another user changed the record

Corel Paradox displays this message when you attempt to post changes to data stored on a SQL server and optimistic locking fails because another user has updated it.

Solution

SQL tables use an optimistic record locking scheme. Corel Paradox does not use optimistic record-locking for Corel Paradox or dBASE tables, however, it will use it for SQL tables because this is the typical SQL locking mechanism.

When optimistic locking fails, Corel Paradox does not post the changes you are trying to save because you could overwrite the new information without ever seeing it. This message warns you that the information you updated is no longer current. Undo the changes you are attempting to post and lock the record again to force a refresh of the remote data. Make the changes you want and post the changes.

For more information on optimistic record locking, see your SQL server documentation.


Couldn't perform the edit because another user deleted or moved the record

Corel Paradox displays this message when you try to post changes to data stored on an SQL server and optimistic locking fails because the record being updated has been deleted or moved.

Solution

SQL tables use an optimistic record locking scheme. Corel Paradox does not use optimistic record-locking for Corel Paradox or dBASE tables, however, it will use it for SQL tables because this is the typical SQL locking mechanism.

When optimistic locking fails and the record you are trying to post is no longer in the same position, Corel Paradox cannot update the record with your changes and displays this message to inform you.

You need to undo the changes you are attempting to post. If the record has moved to a different position in the SQL table, find the record at its new location, lock the record, and make the changes you want. Post the changes when complete. If the record has been deleted, you can add a new record as applicable.

For more information on optimistic record locking, see your SQL server documentation.


Expression in this field has the wrong type

You are using example elements to join two tables, however, the data types of the two fields used for the join are incompatible and cannot be used to link the tables.

Solution

Perform the join using fields of similar data type.


Crosstab or Query contains too many fields

You have included more than 255 fields in your crosstab or query specification.

Solution

Reduce the number of fields included in the crosstab or query.


Could not fit field <...> in layout

There is not enough room to include the field specified by <...> in the design of the form or report, or Multi-record object.

Solution

The following suggestions, alone or in combination, may help alleviate this situation:

•	Remove fields from the design of the document which are not needed.

•	Set field labels off so that fields are unlabelled.

•	Change the style of the document from multi-record to tabular or single record.

In reports, do one of the following:

•	Consider using group bands to group detail records.

•	Reverse the direction of the table links in the data model. Depending on how your data and report are organized, this may help reduce the number of detail fields and still provide the information content.


The ObjectPAL version used in this form is incompatible with this version of Paradox. You must recompile from source
The ObjectPAL version used in this form is incompatible with this version of Corel Paradox. You must recompile from source

You have attempted to open a delivered form or report (.FDL or .RDL) that contains a table whose structure has changed since the form or report was delivered.

Solution

Delivered versions of forms and reports do not contain design window information. Therefore, changes in the structures of tables in the data model cannot be resolved automatically as they are with non-delivered files. You must open the form or report in a Design window (.FSL or .RSL), allow Corel Paradox to note and correct for the structure modifications (or correct them yourself manually), then toggle to view data. You can deliver the updated form or report with the current table structure.


Cannot cut selection to Clipboard

You have attempted to cut an invalid object or selection of objects to the Clipboard.

Solution

To cut a selection to the Clipboard, it must contain object(s) that are suitable for cutting to the Clipboard. Not all objects can be cut to the Clipboard. Cutting certain “sub” objects by themselves puts them out of context and, therefore, you cannot copy or cut such objects to the Clipboard. Examples of these objects are edit regions of fields (without the field object), a record from a Multi-record object (without the Multi-record object), and a header of a table (without the table).

This message also occurs if you select multiple objects from different containers.


Cannot copy selection to Clipboard

You have attempted to copy an invalid object or selection of objects to the Clipboard.

Solution

To copy a selection to the Clipboard, it must contain object(s) suitable for copying to the Clipboard. Not all objects can be copied to the Clipboard. Copying certain “sub” objects by themselves puts them out of context and therefore, you cannot copy such objects to the Clipboard. Examples of these objects are edit regions of fields (without the field object), a record from a Multi-record object (without the Multi-record object), and a header of a table (without the table).

This message also occurs if you have selected multiple objects from different containers to copy to the Clipboard.


Cannot paste from Clipboard into the selected object

This message occurs when you attempt to paste Clipboard data into an object that cannot receive the Clipboard data.

Solution

Follow the solution specified below for individual circumstances that can display the message:

•	There is no object selected to receive the Clipboard data. Select a container object to receive the Clipboard data.

•	The selected object cannot read the Clipboard data. For example, a circle is selected and the Clipboard contains text. The circle does not know how to handle text data and, therefore, the operation is not permitted. A less obvious scenario is attempting to paste text data from the Clipboard into a text object. Select the contents of the text object then perform the paste operation.

•	You have attempted to paste a table frame into an object that already contains a table frame that is bound to the same table. An object cannot contain multiple table frames bound to the same table. Consider using a different combination of object types in the container. For example, you may combine a table frame object and field objects from the same table in the same container.


Chosen container cannot embed or disembed other objects

This message occurs when you attempt to paste Clipboard data into an object that cannot receive the Clipboard data.

Solution

Select an object that can read the Clipboard data. For example, to copy text data from the Clipboard into a text object, select the contents of the text object and perform the paste operation.