4D v16.3
Using 4D Developer Edition 64-bit version
- 4D Design Reference
-
- Introduction
-
- Welcome
- Working environments
- Integrated servers
- Using 4D Developer Edition 64-bit version
Using 4D Developer Edition 64-bit version
With 4D v16, 4D provides 4D Developer Edition and 4D Volume Desktop in 64-bit versions for OS X.
Notes:
- 64-bit versions of 4D Developer and 4D Volume Desktop are available for Windows starting with 4D v16 R2.
- Keep in mind that 4D also allows Using 4D Server 64-bit version (Windows) and Using 4D Server 64-bit version (OS X).
These versions allow your 4D stand-alone applications, as well as your 4D remote applications, to take full advantage of the power of 64-bit operating systems. The main advantage of the 64-bit architecture is that more RAM can be addressed. Moreover, implementing this architecture provided us with an opportunity to support powerful features, such as the ability to handle Preemptive 4D processes, to modernize printing as well as the Quick Report editor, or yet again, to allow your applications to take advantage of Native object animations (4D 64-bit versions on OS X).
Although widely rewritten, 4D 64-bit applications are highly compatible with 4D databases developed in 32-bit versions. However, since they use the most recent technologies, we needed to update some features, as well as to stop supporting others. All these evolutions are detailed in the Specific features of 64-bit versions section below.
4D Developer 64-bit version for OS X requires the following minimum configuration:
| Version | OS X version 10.10 (Yosemite) or higher |
| RAM | 8 GB |
Please refer to the certification matrices available on 4D's Web site to find out which operating systems are compatible with your version of 4D.
4D applications intended for 64-bit architectures are specific versions dedicated to this environment; (they will not run on a 32-bit OS).
In interpreted mode, the same 4D databases can be executed with either a 64-bit or a 32-bit 4D application (server or local). Development is identical regardless of which application is used (except for the limitations listed in this documentation).
In compiled mode, databases must have been compiled for the appropriate processor: 64-bit in order to be executed with a 64-bit 4D application, and 32-bit to be executed with a 32-bit 4D application. A database which has been compiled in 32-bit only and which does not contain interpreted code cannot be executed with a 64-bit 4D application, and vice versa. You can compile your database for just one specific architecture, or for both. For more information about compilation, please refer to the next section.
The following table summarizes compatibility between the various 4D execution environments and the database code:
| Available code | 4D Dev 32-bit | 4D Dev 64-bit | |
| 4D Server 32-bit | Interpreted | OK | OK(*) |
| 32-bit compiled only | OK | - | |
| 32-bit and 64-bit compiled | OK | OK(*) | |
| 4D Server 64-bit | Interpreted | OK | OK(*) |
| 64-bit compiled only | - | OK(*) | |
| 64-bit and 32-bit compiled | OK | OK(*) | |
| Local database | Interpreted | OK | OK |
| 32-bit compiled only | OK | - | |
| 64-bit compiled only | - | OK | |
| 32-bit and 64-bit compiled | OK | OK |
(*) With 32-bit versions of 4D Server (both platforms) and 64-bit versions of 4D Server for Windows, you need to make sure that the ServerNet network layer is activated on the server side, since the legacy network layer is not available in 64-bit version of 4D. For more information, please refer to the New ServerNet Network Layer (compatibility) section.
The following plug-ins and components can be loaded and executed interchangeably by 4D Server, 4D Developer Edition or 4D Volume Desktop in 32- or 64-bit versions:
- 4D for OCI
- 4D Internet Commands
- 4D ODBC Pro
- 4D Pack
- 4D Progress
- 4D SVG
- 4D Widgets
- 4D Write Pro Interface
4D View and 4D Write
4D View and 4D Write are 32-bit plug-ins and normally can only be used with 32-bit versions of 4D. However, 4D provides the following arrangements:
- Non-executable 64-bit versions of these plug-ins are available as placeholders so that developers can load them and work in 4D 64-bit versions and then compile/deploy for 32-bit versions.
- 4D Server 64-bit for Windows can execute these plug-ins in faceless mode (no interface).
This section covers particularities and evolutions concerning the implementation of the current 64-bit versions of 4D Developer Edition and 4D Volume Desktop on OS X.
Many 4D features and dialogs have been adapted or even rewritten to support the 64-bit architecture. Most of the changes are transparent and will work just like in 32-bit releases. However, some editors have been modified and now differ from their 32-bit versions, and some elementary features such as printing have been updated.
| Feature | Comment |
| Quick Report editor | Completely rewritten. See Quick reports (64-bit) section. |
| Label editor | Completely rewritten. See Label editor (64-bit) section. |
| Charts | The GRAPH command accepts an Object type parameter that allows you to define graph settings. |
| Printing | Update of "Printing" dialog boxes (use of standard system dialog boxes). The "Print settings" dialog box is no longer displayed automatically (see the PRINT SETTINGS command). Modification of the SET CURRENT PRINTER and SET PRINT OPTION commands. |
| Import/Export dialog boxes | Work as in 32-bit version, except XSL support for XML exports (XSLT is no longer supported, see below) and via an ODBC source (disabled, see below) |
Some features are disabled in the 4D Developer Edition 64-bit version:
| Feature/Technology | Comment |
| Import/Export via ODBC Data source | Disabled |
| Quick Report cross-table reports | Disabled |
| Quick Report editor: borders | Disabled |
| Quick report editor: programmatic control of the interface (QR ON COMMAND, QR EXECUTE COMMAND) | Disabled. The "ribbon" interface type can't be programmatically controlled in the new editor. Use the included box and other "QR" commands if you want to create a custom interface. |
| Label Editor standard codes | Disabled |
| Using integrated Web Kit in Web areas | Disabled. If option used, automatic switching to system Web engine. Under OS X, access to 4D $4d methods is maintained |
The following deprecated features or technologies are not supported in the 4D Developer Edition 64-bit version:
| Feature/Technology | Comment |
| XSLT with Xalan | _o_XSLT APPLY TRANSFORMATION, _o_XSLT SET PARAMETER, and _o_XSLT GET ERROR do nothing. Use the PROCESS 4D TAGS command or the PHP libxslt module instead. |
| PICT format | 'Unsupported image format' picture + file extension is displayed instead. PICT format is globally deprecated in 4D, see also Pictures in PICT format. |
| QuickTime | QuickTime for pictures is not supported. The QuickTime support database parameter is ignored. |
| cicn icons | GET ICON RESOURCE command is not supported; it returns an error. |
| Database .RSR files | Database .RSR files are not opened automatically. You need to use Open resource file. |
| Writable resource files | _o_Create resource file is not supported; you can only open resource files in read-only. |
| _o_Font number | This command is not supported; it returns an error. |
| _o_Open external window | This command is not supported; it returns an error. |
| Legacy network layer | Only ServerNet is supported. |
| ASCII compatibility mode | Only Unicode mode is supported. |
| 4D Write and 4D View plug ins | Use 4D Write Pro Reference and 4D View Pro. |
| AP Print settings to BLOB / AP BLOB to print settings (4D Pack) | Replaced by the Print settings to BLOB / BLOB to print settings commands. |
Product: 4D
Theme: Introduction
Created: 4D v16
4D Design Reference ( 4D v16.1)
4D Design Reference ( 4D v16.3)
Inherited from : Using 4D Developer Edition 64-bit versions ( 4D v16)
