PRODUCTS

MIGRATING TO 4D v12

Smooth Migration

4D
With all the benefits that come from adopting the latest and greatest technologies, there are perceived challenges. We're here to help ensure that your migration to 4D v12 is easy and smooth.

Benefits galore

With all the features introduced in 4D v12, you have every reason to upgrade. Not only does it bring you the ingenious little features developers and users have been asking for, but it introduces some amazing timesavers that you'll soon wonder what you ever did without.

 

From a more efficient Method Editor to Form Widgets to the ability to execute PHP, 4D v12 can cut down development time, while letting you deliver the features that will put a smile on users' faces.  For an overview, you can read more about what's new in 4D v12.

 

 

Migrate with comfort

If you're thinking about migrating from 4D v11 SQL, you haven't a worry in the world. When your solution is opened in 4D v12, it is fully converted – including the modification of all updated commands – and the migration should be seamless.  

 

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

 

Of course, we want you to successfully migrate to 4D v12, 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 v12, which are:

 

 

Windows

Mac OS

 Processor

Pentium 4

Intel*

 OS version

Windows Vista, Windows XP, Windows 7

Mac OS X 10.5 and higher

 RAM

1 GB (2 GB recommended)

 Screen resolution

1280 x 1024 pixels

 

(*) IMPORTANT: Note that the Mac OS version is not compatible with PowerPC computers.

 

 

Migrating from 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 structure to 4D v12 are:

  • (work on copies, of course)
  • Open the structure with 4D v12, 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 v12, you can’t open it with a previous version. For the data file, things are a bit different. If…

  • with 4D v12, you have never used the new Replication/Synchronization features…
  • and, with 4D v11 SQL Release 6 (11.6), you select the “Allow opening v12 data file” option in the “Database” preference pane…

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

 

Miscellaneous
 

  • The only change in the licensing scheme between 4D v11 SQL and 4D v12 concerns 4D SQL Expansion: You can now use it for a 2 CPU machine, regardless of the number of embedded cores.
  • If the structure was an old structure, not created with 4D v11 SQL, 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.

 

 

Migrating from 4D 2004

If you are new to the 4D v11 SQL/4D v12 architecture (Server architecture, database context for triggers, Unicode handling, natively supported image formats, etc.) then you should first read the conversion document that can be found in the "Expert" area of the 4D Doc Center, under the 4D v11 SQL tab.
 

Convert the structure/data


The process for converting a structure from 4D 2004 to 4D v12 is fully described in the Upgrade Manual. As a reminder, here is what's going to happen when 4D v12 opens a pre-v11 structure:

  • 4D v12 opens the Conversion Dialog
  • Within this dialog, you can set several options (such as selecting the data file, checking the box that allows the On startup method to not be executed, etc.)
  • Once validated, 4D first makes a copy of the original files, and then it converts the structure and its data file. You won’t be able to open the structure or the data with older versions.
     

 

Deprecated features

Whatever the origin of the structure (4D v11 SQL 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 v12 migration:

 

  • 4D Doc Center: The 4D v12 Upgrade Manual references all the changes in 4D v12.
  • 4D v12 Resources: You'll find many videos, "How Do I" examples and example applications, as well as compatibility tables, etc.
  • 4D Knowledgebase: Search for numerous tech tips about 4D v12, as well as the latest Tech Notes available for 4D Partners.
  • Training Center: The fastest way to learn about 4D v12 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 v12!