Product

New architecture for application deployments

Today, merged applications save many information in the application package and also in the compiled file (.4DC). Besides preventing to create read-only applications, saving information in the application package has another annoying consequence: the information gets lost when you update the application.

Product

Report duplicates in unique fields

In 4D v15 R3, the way to detect duplicates in fields declared as unique has been enhanced so that users have a mean to know which are the offending fields.

What’s new? All the offending fields are now displayed in an error message or in the log.

Duplicates can be reported through 2 different ways:

  • when 4D needs to create indexes on a database with offending fields.
  • during an MSC Verify scan.

Product

REPLACE STRING is faster

In 4D v15 R3, the algorithm of the REPLACE STRING command has been enhanced to make replacements on large amounts of data faster. In our tests replacing 32,000 occurrences, the new algorithm makes the command an average of 4000 times faster than the old one.

Product

Quick Report Editor fully rewritten

With 4D v15 R2 is available the first preview version of the 4D Developer Edition 64-bit Mac & Windows. This preview includes dialogs that have been fully rewritten, first to migrate to 64-bit but also to provide you with modern end-user dialogs with an improved user experience.

Product

Label Editor has been redesigned

4D v15 R2 includes the first preview version of the redesigned Label Editor which is fully implemented in 4D code.
The new dialog is available in the 4D Developer Edition 64-bit versions (Win & Mac). It can be accessed through the Tools>Labels menu.

Product

Improvement for Product activation

The 4D product license activation has been improved in 4D v15 R2.

First activation by entering a single number

When you use a 4D Server, you need additional 4D Client, 4D Write, 4D View, and many others expansions. Then, you receive 5, 10, 20 or more license numbers to enter manually in your product.

Now, in v15 R2, you enter only the 4D Server license number, and your 5, 10, 20 and more expansions are also activated.

Product

Avoid the “Select data file” dialog to show up for a new deployed app

When you deploy an application to your customer, either a merged 4D Server or Single User application, 4D usually opens the “Select data file” dialog. This happens because for an updated solution 4D cannot find the position of the last used data file, as you just replaced the old structure. And for a first time usage, 4D does not know where you would like to create the data file – so it asks for the location.

This dialog, as the very first interaction with your application, might be confusing for the customer. And the verification for the data file happens before the On Startup is executed, before your code has a chance to select another file. To avoid this, 4D v15 introduces a new feature, named Default Data.

Page 59 of 60