Principles for conversion

• You must have an "interpreted" version of the database (xxxx.4DB file for the structure), as well as the Designer password to perform a conversion;

• Make a copy of your database before conversion;

• Perform a syntax check. Even if you do not want to compile your database, this check can help warn you about possible errors;

• Use the Maintenance and Security Center to check and repair the structure and data;

• Check whether you have any PICTs using the 4D Pack AP Is Picture Deprecated command (introduced in version 13.2) and convert them using the TRANSFORM PICTURE command (in 4D v14, there is still the possibility of using QuickTime by means of a new selector for the SET DATABASE PARAMETER command);

• (Optional) Possible to implement primary keys if data journaling is needed (starting with version 13.4) (see Primary keys in the Design Reference manual).

• Since version 13.5, it is mandatory for Unique fields to be indexed. You will no longer be allowed to create/modify any records for a non-indexed Unique field: attempting to save the record will generate an error (-9998 Unique record exists, 1088 Index is invalid or missing). To create missing indexes, or generate a disk file listing all the non-indexed fields, refer to the appendix: "Methods used for conversion".

Databases created with version 14 of 4D or 4D Server (as well as ones created in v11, v12, et v13) are compatible with 4D version 15 (structure and data files). You can convert any interpreted structure file. To do this, just launch 4D v15 and open your structure file (xxx.4DB file) in interpreted mode.

A dialog warns you that the structure file is going to be converted:

After your structure file is converted to 4D v15, it can no longer be opened using a former version.

Then a second dialog appears:

Your data file is also converted to version 15 but it can still be opened and used with 4D version 14 R5 or 14.4.