Embed deployment license automatically into your applications
You’ve built the app. Now you need to ship it — fast, clean, and licensed. With 4D 20 R10, you can automatically embed your deployment license into yo...
You’ve built the app. Now you need to ship it — fast, clean, and licensed. With 4D 20 R10, you can automatically embed your deployment license into yo...
In previous versions of 4D, developers could request evaluation licenses for development purposes, but providing end users with evaluation versions of...
This new feature improves the local resources management of 4D Client merged applications executed with Windows Remote Desktop Services. Lets’ see how...
In our ongoing effort to improve the building of 4D applications, we've added a few functionalities to 4D v19R5 that you'll certainly find useful. Th...
Projects introduced the new directory.json file containing users, groups and permissions. It allows authentication, restrictions, permissions on sever...
You may want to restrict administrators from accessing the Data Explorer and the Runtime Explorer in your deployed merged servers. 4D v19 R5 enables t...
As a publisher, you sometimes want to duplicate a merged client application to connect each of them to their dedicated 4D Server. Let's see how to do ...
The release of Silicon Macs had a great impact on the way 4D compiles applications. Before v19, 4D was compiling only for Intel architecture, using th...
To prevent session loss, 4D monitors the sleeping state of remote 4D applications. When a user is connected from a remote 4D application to a 4D Serv...
When generating .4dz files, 4D uses a standard zip format by default. If you are a software publisher, you'll be happy to know that 4D v19 R2 added a ...
Got a question, suggestion or just want to get in touch with the 4D bloggers? Drop us a line!
* Your privacy is very important to us. Please click here to view our Policy