"No Primary Key" errors

FM/Db2 reports a "No Primary Key" error if your change would have created a foreign key value for which there is no corresponding primary key in the parent table of the relationship. This is a referential integrity (RI) constraint error. The prefix area error indicator only shows an R in the rightmost position if the parent table is different to the table currently being edited.

You can use the foreign key indicators to identify columns of the table that are defined as foreign keys.
Note: The foreign key information is only available if the Retrieve foreign key information when building templates option was selected when the template for the object was built.

The error information panel for this error shows the names of the parent and dependent tables in the relationship that caused the error, and the name of the relationship. At the bottom of the panel are the names of the columns that comprise the key in both the parent and dependent tables, along with the value that caused the error.

If the parent table is different to the dependent table, you can enter the RE prefix command against the row, or enter the REDIT primary command from the error information panel, to edit the parent table of the relationship and correct the error.

Related tasks

Related references