Table 81: FILL( ) method modes
|
|
|
|
APPEND
|
Fills the table by adding new records on top of existing records in the table, without performing any record comparisons. If this creates duplicate records, the AVM generates a run-time error and you must manage the duplicate records.
If you are certain there are no duplicate records, an APPEND is more efficient than a MERGE.
|
|
EMPTY
|
Empties the table before the FILL operation begins.
|
|
MERGE
|
Fills the table by merging new records with existing records in the table. The FILL( ) method checks each record to ensure there are no duplicate records (based on the table’s unique primary index). If the FILL( ) method finds a record with a duplicate key, it does not replace the record because the record might have dependent records elsewhere in the ProDataSet. In this case, the AVM does not generate a run-time error. Thus, you cannot use this mode to refresh existing records.
|
|
NO-FILL
|
Does not perform the FILL operation on the table.
|
|
REPLACE
|
Fills the table by replacing existing records in the table. The FILL( ) method checks each record to determine whether or not it exists in the table (based on the table’s unique primary index). If the record exists in the table, the FILL( ) method replaces it. If the record does not exist, the FILL( ) method creates a new record. The BEFORE-ROW-FILL event handler is run after the original ProDataSet row is copied into the ProDataSet buffer. A REPLACE is less efficient than an APPEND or a MERGE.
|
