Converting databases from previous versions

Databases created with versions 11.x, 12.x and 13.x of 4D or 4D Server are compatible with 4D v14 (structure and data files).

• Database files in versions prior to 11 must be converted through a wizard and can no longer be opened with their original version.
• Version 11 or 12 database files are converted directly to version 14 and can no longer be opened with their original version.
• Structure files in version 13 files are converted directly to version 14 and can no longer be opened with their original version. However, data files in version 13 can be opened in version 14 without converting them so in this case they could be opened in version 13 again.

Note: You can convert any interpreted structure file. The file may contain compiled code; in this case, you will need to recompile the database after its conversion.

If you are converting a database prior to version 14 that is missing primary keys, a warning dialog box will appear. This point is detailed in the "Primary key error window" paragraph below.

A database from version 13 is converted directly when you open it with 4D v14. A warning dialog box lets you know that the structure file is going to be converted and that you can no longer open it with an earlier version.

Data files, however, are opened without conversion so they can still be opened again in version 13.

A database from version 11 or 12 gets converted directly when you open the structure file with 4D v14. Two successive warnings let you know that the files are being converted and that you can no longer open them with an earlier version.

Note that when you convert a data file, its indexes are rebuilt.

Note: For information about converting databases from an earlier version, refer to the Converting databases from previous versions in the 4D v13 documentation.

Starting with 4D v14, the use of a log file requires all the journaled tables to have a valid primary key (see Managing the log file).

An error dialog box is displayed when at least one table in the database does not have a valid primary key.

This dialog box can appear:

• after conversion to v14 of a database,
• after checking the Use Log File option in a v14 database.

Note: If journaling is not enabled in the database, the error dialog box offers you the option to open the database despite the primary key error.

If you have access to the database structure, the dialog box provides several options and displays, when you expand the lower area, the list of tables that do not have a primary key:

You then have the following options:

• Copy: copies information from the window into the clipboard for analysis.
• Close database: leaves the database intact and closes it.
• Continue: opens the database without processing the errors. In this case, journaling is disabled for the database (if the Use Log File option was checked, it is unchecked) and the database works perfectly in v14. You can use this option if you do not want to use the log file with your database.
• Run assistant: displays the Primary Key Manager window, used to update all the tables of the database. We recommend choosing this option in order to evolve the database. This assistant is described in the Creating a database structure section.

If you do not have access to the database structure, it is not possible to enable journaling and 4D will display a message recommending that you contact the database administrator.

4D v14 can open v13, v12 or v11 components (compiled or interpreted) directly without conversion or a confirmation dialog box. Remember that components are always open in read-only mode.

You do not need to recompile components but conversion to v14 is only possible for .4DB files and not for .4DC ones.