Benefits galore

With the features and added ease of use introduced in 4D v13, you have every reason to upgrade. Not only does it support an increasing number of technological standards, but it brings unprecedented productivity to both developers and end users.

From enriched list boxes to integrated Webkit to code introspection, 4D v13 brings forth features that increase usability, enhance performance, and assist in maintenance.  For an overview, you can read more about what's new in 4D v13.

Migrate with comfort

If you're thinking about migrating from 4D v12, you haven't a worry in the world. When your solution is opened in 4D v13, it is fully converted and the migration should be seamless.  

On the off chance that a problem occurs, you can backtrack to your data file 4D v12 (see below) without your solution being affected. 

Of course, we want you to successfully migrate to 4D v13, so we'll arm you with the information you need...

Minimum Configuration

Before migrating your application, check that the operating system and the machine match the minimal requirements for 4D v13, which are:

(*) Under Windows XP, 4D v13 does not support the integrated Webkit rendering engine.

Migrating from 4D v12 or 4D v11 SQL

Convert the structure/data

In this situation, converting the database is as simple as validating the confirmation dialog. That’s all. So the basic steps for converting a 4D v11 SQL or a 4D v12 structure to 4D v13 are:

• (work on copies, of course)
• Open the structure with 4D v13, accept the dialog
• Once this dialog is validated, 4D will also ask to convert the data file

As usual, once the structure file is converted to 4D v13, you can’t open it with a previous version. For the data file, things are a bit different. You can revert your data to v12, if…

• with 4D v13, you have never used the new external storage features,
• and, with 4D v12.3 or later, you select the “Allow opening v13 data file” option in the “Database” preference pane…

… then you will be able to open this data file with the v12.3 copy of the structure.

On the other hand, you can't directly revert a data file from v13 to v11 SQL.

Miscellaneous
 

If the structure was an old structure, not created with 4D v11 SQL or later, then we recommend that you read the “Conversion to 4D v11 SQL” document that is available in the "Expert" area of the 4D Doc Center, under the 4D v11 SQL tab.

If backtracking....
If for some reason you need to revert your data file to 4D v12, you must reconstruct your index under the older version of 4D (just drop the .4DIndx file before launching 4D v12) and then compact the data file.

Deprecated features

Whatever the origin of the structure (4D v12 or earlier), we strongly encourage you to read the “Deprecated Features" document, available on our Compatibility page. It will warn you about features that are considered as deprecated, and that may be removed in a future major release. This information will make it easier for you to update your code when (and if) necessary, and your application will remain compatible with the newest versions of 4D and operating systems.

Useful links

Please consider the following helpul links that should help you achieve a successful 4D v13 migration:

• 4D Doc Center: The 4D v13 Upgrade Manual references all the changes in 4D v13.
• 4D v13 Resources: You'll find "How Do I" examples and example applications, as well as compatibility tables, etc.
• 4D Knowledgebase: Search for numerous tech tips about 4D v13, as well as the latest Tech Notes available for 4D Partners.
• Training Center: The fastest way to learn about 4D v13 is to follow one of our regular training sessions. Just ask us for more details.
• Finally, if any issues occur during your migration, don't hesitate to contact our tech support team.

We wish you a happy and productive migration to 4D v13!