Thoughts and reflections on 4D World Tour 2019
Blog post by guest author Kirk Brooks, a 4D developer from San Francisco:
Visiting 44 cities around the world to bring all the latest 4D developments, 4D World Tour 2019 finally arrived in Atlanta on April 8–9th 2019. The two-day event featured sessions and workshops with the 4D team. For me, this was the best World Tour so far . . . and I’ve been to them all!
The first day is free and in previous World Tours, day one was more of a sales pitch and feature overview. Not this time! There were 17 demo databases to highlight and present many of the new capabilities involving ORDA, Form, dynamic forms, and a more refined preview of 4D for iOS. There were a lot of useful elements you can pull right into a project.
4D Write Pro: a new way to set TABS!
We’re thrilled to announce an exciting enhancement in 4D Write Pro! In addition to the features we’ve rolled out so far, 4D v17 R5 also includes a new feature for tabs.
Convert an existing database into a Project
As of 4D v17 R5, you can create a database project. One of the greatest benefits of projects is how easy it makes collaborative work for distributed teams … by storing the source in a source control system in plain text files. Whether you’re a single developer or part of a team, this opens a new world of possibilities.
But what about existing databases? Can they be converted to projects? Yes! This blog post is all about showing you how to do this and making you aware of a few things to know before proceeding.
Compatibility settings – all the rest (Part 4)
We began a series of blog posts on compatibility settings and the secret options that can drastically help improve the performance and behavior of your applications (QUERY BY FORMULA, Transactions and period and comma). This final post of the series will give an overview of the remaining settings.
Compatibility settings – Nested Transactions (Part 3)
Welcome to our ongoing series about compatibility settings and “hidden” features for improved performance. In the first post, we looked at the QUERY BY FORMULA command and its impact on an application’s behavior. The second post was about the “Use period and comma as placeholders” compatibility option to avoid running into “the numbers are displayed as >>>>>>>>>” hassle.
In this third installment, we’re going to explore Nested Transactions.
Work with .xlsx documents using 4D View Pro
Do you need to open a Microsoft Excel document directly in your 4D View Pro area, or convert a 4D View Pro document to Microsoft Excel format to send it to a customer? It’s now possible! Thanks to this feature, your 4D business applications have taken a further step towards better compatibility with the MS Office environment.
Compatibility settings – Use period and comma as placeholders (Part 2)
We’ve started a series of blog posts on compatibility settings and the secret options that can drastically help you improve the performance and the behavior of your applications. The first post was about QUERY BY FORMULA.
The second part of the compatibility series is about international usage of your business applications. This could mean selling to other countries – or having coworkers coming from other countries to work for a while, but using their local systems.
If you’ve ever seen or gotten reports like “the numbers are displayed as >>>>>>>>>”, this blog post is for you.
Compatibility settings – or driving with the parking brake on(Part 1)
In code kitchens, I usually spend some time with the database settings, especially with the Compatibility settings. Often certain settings don’t follow best practices and during discussions with the application developer, I hear “oh, I never changed these” or “I’m not sure about the impact, so better not touch them”.
Since they could drastically impact the performance or behavior of your applications, we’ve begun a series of blog posts to discuss some of these “secret” settings.
Times inside objects… (and everywhere else)
Objects are at it again, continuing to demonstrate their utility to ease your life as a developer.
Using time (or duration) values inside of objects is now smoother and more intuitive. Beginning with 4D v17, times inside objects are set as seconds – and not milliseconds!
Dates inside objects!
Objects are great! Their flexibility, combined with speed and elegance, make them a first choice for most developers. Using dates inside objects is now easier and more intuitive. From now on, dates can be set as dates – and not strings inside objects!
Contact us
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