4D has been a longtime supporter of team development, ever since 4D Server 1.0. The greatest benefit of working together on the same source code, is allowing both team development and team testing. However this can create some disadvantages for distributed teams since they may not be able to work on the same source.
Following a complete rewrite, 4D now supports two ways to work with sources: binary and project. Binary is the 4D we all know and love, with the source in a binary file to allow team development with 4D Server. Project makes it easier for distributed teams to work collaboratively by storing the source in a source control system in plain text files.
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.
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.
Imagine transferring €200,000 from one bank account to another. You withdraw the amount from the source account, and then you deposit it in the destination account. So far everything is normal and in a perfect world the operation will succeed. Unfortunately, here in the real world things can go wrong. Something happens and the money is lost. That’s very bad.
Well, transactions are here to ensure that this doesn’t happen with your applications! In this blog post explore in detail the use and importance of transactions, as well as several scenarios showing how they can save your business.
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.
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.
Today, big screens are everywhere. At the airport or train station for arrival/departure. In production areas for failure/success or production numbers. In call centers for activity or calls in queue. In stock exchange for a ticker.
Your first thought could be to use a normal computer, macOS or Windows, with a “27” or 30” screen. Expensive, but easy to do. But besides the high price, you need to run a 4D app, launch it, update it, all just to display a picture?
Security is an important and fundamental topic for a database or business solution system. This article proposes an overview of how 4D protects your data. In fact, security is about data protection. And data protection is a huge area. Data needs to be protected for unwanted access, but also for loss.
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