|
<< Click to Display Table of Contents >> Restructure Extended, Paradox |
  
|
|
<< Click to Display Table of Contents >> Restructure Extended, Paradox |
|
Except for the general issue loosing validity checks when restructuring tables via the extended method (rebuilding tables), restructuring Paradox tables operates smoothly preserving all datatypes thanks to the mutual compatibility between the generic field types and Paradox data types.
DBDemos Biolife as a Paradox table
Though offering the extra Required attribute, this method has some issues to take into account:
As this method of restructuring is based om recreating the table as a mirrored data copy, other existing validity checks as MinValue, MaxValue and DefaultValue, as well as Referential Integrity settings will be cleared!
So, do NOT use this method if it is considered essential to preserve other validity checks or Referential Integrity.
See also Table Validity Checks.
Though clearing the Value Check conditions, the restructuring will preserve all indexes.
Using a different technology than the basic restructure dialog, rebuilding the table, if containing an Autoinc field, this will be re-initialized and reallocated with new sequential values.
The Required attribute is supported by all Paradox table levels.
You may experience the selected required check mark disappear after clicking the Restructure button.
This will happen if selecting the Required check for an Autoinc field, as this field type always auto fills when adding records, and thus does not need or accept the required attribute.
If for any reason the restructuring is not successful, the procedure is always creating a temporary backup file
{TableName}_TempXXXXXX.db(f), which you can access and rename into the original table name (after deleting that). The Temp file is auto-deleted when the procedure terminates normally.
The XX.. of the Temp-file representing a six digit hexadecimal random number in the range 0 to FFFFFFh (0 to 16.777.215).