Changing from 32-bit versions to 64-bit versions

4D v17 works in 32-bit or 64-bit, macOS ou Windows.

Upgrading a 32-bit 4D application to a 64-bit version requires some preparation work.

The entire 64-bit 4D product line no longer depends on Altura's Mac2Win library. Altura's Mac2Win is now completely removed from 64-bit versions of 4D Developer Edition and 4D Volume Desktop, allowing these products to fully utilize modern Windows APIs:

• 4D Developer Edition and 4D Volume Desktop Windows 64 bits in v17 (since v16R2)
• 4D Server Windows 64 bits in 4D v17 (since v16 R4)

Note: 32-bit Windows versions of 4D still use Mac2Win.

4D Developer Edition 64-bit integrates new label, quick report and import-export editors ... modern, intuitive and easy to use!  You can launch multiple instances of 64-bit 4D Developer Edition on your computer without having to install the application twice.

If your application works with a Windows or macOS 64-bit 4D Server, most of the work is already done. 64-bit single-user applications may require additional steps. This section provides a point-by-point checklist to help you check all the necessary steps before and after the upgrade.

Several features have been updated, disabled, or even declared obsolete with the 64-bit migration of our products. All the details are listed in the Using 4D Developer Edition 64-bit versions section .

Note: As with any upgrade process, it is recommended that you use the MSC and run a check before each important step, to ensure that the data and structure are valid.

 The first requirement consists in upgrading your plug-ins (if any) to their 64-bit version:

• 4D plug-ins:
  All plug-ins already exist in 64-bit versions, except 4D Write and 4D View.
  
  • If your application uses 4D Write, you should consider migrating your code to 4D Write Pro. A good practice is to keep your existing 32-bit code and separately start a new 64-bit based module with 4D Write Pro alongside it. If, during a transitional period, you want to have both your 4D Write and 4D Write Pro documents, you should use 4D v17 32-bit.
  • If your application uses 4D View, you will need to use 4D View Pro or other alternatives.
• Third-party plug-ins:
  Contact your providers to get 64-bit versions.

1. Upgrade your application to the latest 32-bit release, for example 4D v17 32-bit or higher.
2. Verify that Unicode mode is enabled.
   
3. Convert all your PICT/cicn/QuickTime images .
   To detect obsolete image formats in your data, you can use the GET PICTURE FORMATS command.
   You must also replace any unsupported image formats in your database structure. A check using the MSC will allow you to detect all obsolete images in the resource files for image buttons, 3D buttons, and static images.
4. Replace all XSLT-based features (_o_XSLT APPLY TRANSFORMATION, _o_XSLT SET PARAMETER or _o_XSLT GET ERROR commands), with the PROCESS 4D TAGS command, for example.
5. Replace _o_Font number calls with font name calls.
6. Remove any code that creates or modifies resource files.

At this point, you are ready to open your application with a 64-bit version of 4D.

1. Open your application with a 4D Developer Edition 64-bit version.
2. If you use the integrated WebKit for your Web areas, check them since they are automatically switched to the System engine (access to 4D methods through $4d is still valid).
3. If your code uses the Mac spool file format option of the SET PRINT OPTION command, you need to replace it with a call to SET CURRENT PRINTER with the Generic PDF driver constant.
4. Check Label editor calls and usages (refer to Label editor (64-bit)).
5. Check Quick Report calls and usages (refer to Quick reports (64-bit))

Your application is now fully 64-bit compatible and you can benefit from all the new 64-bit features in 4D.

In particular:

• The 64-bit architecture pushes back database cache limits. Improve your database's performances simply by using a larger cache.
  Adopt powerful 64-bit features such as preemptive processes, animated form objects, or new printing features.
  Build your applications with 4D Runtime Volume License 64-bit..
  Use final 64-bit versions of 4D Server on Win and macOS - refer to the Using 4D Server 64-bit version (OS X) and Using a 64-bit 4D Server (Windows) sections

• New Quick report editor, compatible with reports created using previous versions. See Quick reports (64-bit).

• New Label editor, compatible with label files created using previous versions. See Label editor (64-bit).

• Create graphs using an Object type parameter with the GRAPH command.