A new step has been reached in 4D v16 R2 with the 64-bit Quick Report editor: the cross-table reports are now available!
As you probably already noticed, the new Quick report for 64-bit versions had been fully redesigned since v15 R3 to provide you and your end-user with a better user experience. After list reports which were available as the very first step, we are now moving forward and delivering cross-table reports.
Want to do generic programming using listboxes? So this feature is for you!
With 4D v16 R2, 20+ new listbox properties can be dynamically manipulated by code so 4D Developers now have the full control over the listbox form object! Among a long list: multi-style, wordwrap, single-click edit, truncation mode, column min & max width and much more. The properties apply to the entire list box, its columns, or both.
No more property available only in Design Mode through the Property List: every single property can now be set and get using 2 commands: LISTBOX SET PROPERTY and LISTBOX Get property.
64-bit is the way where everybody needs to go. 64-bit allows you to take advantage of the power of the 64-bit machines and of the latest native system features for your business application.
With 4D v16 R2, 4D has reached a major milestone as 4D Developer Edition and the 4D Volume Desktop Windows 64-bit are now released as “Final” and are thus ready for production.
Start early, use it now and share your feedback through in the beta version forum from 4D Forums!
At each 4D release, object fields become more and more powerful.
A new 4D command for sorting your record selections according to one or more attributes is now available with 4D v16 R2. The new command ORDER BY ATTRIBUTE works the same as the command ORDER BY; you just have to pass an attribute path by which you want to order your selection – easy!
A new step is reached to provide our developers with a fully customizable listbox object, entirely adaptable to user need. A new option is available in the listboxes that will allow to improve final interfaces: this option is called “Hide selection highlight”.
With just one click this option can be activated. Once activated, the system highlight will be completely invisible.
Did you know that you can retrieve very detailed information on a table, field, indexes, relation or even on the complete database structure? This kind of information is always very useful for analysis or introspection purposes. Of course, you could use the 4D Pack deprecated commands: _AP Get field infos and _AP Get table info. Another option is to use the SQL system tables.
None of them allows you to retrieve all information. So why use a plug-in or SQL when you could use a 4D command? The EXPORT STRUCTURE command returns the complete database structure definition in an XML tree. This command exists since 4D v14 R4.
If your users are running your application as a virtualized application, chances are high they use VMWare vSphere (Hypervisor ESXi) and are using snapshots.
4D v16 R2 will automatically install a VSS writer service. VSS stands here for Volume Shadow Copy Service. When the VMWare administrator starts a snapshot, VMWare informs the guest, which informs the VSS writer, which will inform 4D Server to flush the cache and wait for one second. Then it will inform the OS that the .4DD, .4DIndx and .Journal files belong together and must be snapshot at the same time. The OS will handle this and 4D Server can continue to handle client requests. The “freeze” lasts around a second, usually not even noticed by connected users.
With 4D v16 R2 you can display a graphical horizontal ruler at the top of the 4D Write Pro area ! Thanks to this horizontal ruler, the text can be easily formatted.
Prior to the existence of this graphic ruler, tabulations could only be managed by programming or using the 4D Write Pro interface widget. From now (4D v16 R2 and above), when the ruler is displayed (this is optional) the final user will have the opportunity to manage margins and tabulations easily and graphically.
4D v16 introduced a new fully optimized cache manager for the 64-bit product line. 4D v16 R2 is giving power to our advanced 4D developers to take control by themselves!
The cache manager internal algorithm is based on a priority concept associated to each object type to store in the cache memory. By default, the cache manager algorithm assigns a higher priority value for an index than for records. And recently used objects (records or indexes) have a higher priority to remain in the cache than objects that have not been used in the last two days, etc…
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