Bde.DBTables.TBatchMove.KeyViolTableName
Delphi
property KeyViolTableName: TFileName read FKeyViolTableName write FKeyViolTableName;
C++
__property System::Sysutils::TFileName KeyViolTableName = {read=FKeyViolTableName, write=FKeyViolTableName};
Properties
| Type | Visibility | Source | Unit | Parent |
|---|---|---|---|---|
| property | published | Bde.DBTables.pas Bde.DBTables.hpp |
Bde.DBTables | TBatchMove |
Description
Specifies the name of a Paradox table that will be created to contain all records from the Source that cannot participate in the batch operation because of integrity or key violations.
Use KeyViolTableName to obtain a table of records that could not be applied to the Destination table because of integrity or key violations. KeyViolCount has the number of records in the table that is created.
Key violations occur when appending records to a table that has a primary key. On a table with a primary key, no two records may have the same values on all of the key fields. If a record that is being appended has the same values on all the key fields as a record in the destination table, it cannot be appended.
Integrity violations occur when deleting, appending or updating records to a table that has a referential integrity specification. A referential integrity specification requires that certain fields in one table must have values that exist in a particular field of another table. If a record that is being added does not match the restrictions imposed by referential integrity, it cannot be added. If deleting record would cause tighter referential integrity restrictions that another table cannot meet, it cannot be deleted.
Note: If AbortOnKeyViol is true, then there will be at most one record in this table because the operation aborts with that first record.