With the new network layer, we can implement new functions that were impossible with the legacy network layer. The first is the application sleep notification.
When integrating the log file, 4D stops at the first error and doesn’t return any error message. Reasons for integration errors could be a damaged log, by example because of a bad hard disk or software error during writing. If that error happens at the end, no problem; but it could also be at the start or in the middle of the log. In this case, the data after the error might be useful.
Now, when the integration fails in standard mode, you can try integration in auto-repair mode. In this case, 4D tries to resolve the error encountered, doesn’t stop the integration, and returns the error list.
In 4D applications, the data file is important, so all the activity of the database is stored in the log file. As you all know, the log file is a vital element for the restoration of your database following an unfortunate contingency. However all the information on the database activity may also be useful for analysis. For example, to check the activity on a table, to see the changes made by a user, and to follow a record’s history.
The WEB Session commands have been adapted to 4D Mobile session. Now, you can save the results of a query or an inter-process variable related to a given 4D Mobile session. For example, with new handling of 4D Mobile sessions, you can manage the cart of your users.
This feature is useful when you need to perform, from within a transaction, certain operations that do not need to be executed under the control of this transaction.
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.
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.
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.
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.
Now, you can start 4D v15.0 in a given language while your Mac OS system language is different. For example you want to start 4D v15.0 in Spanish on an English OS X.
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