4D Write Pro and the UI widgets

4D Write Pro has no default interface because it’s meant to be embedded in your application. Therefore, it needs to fit your user interface design and provide just the right amount of features for your use case(s). We decided to provide you an easy way to create your own interface with Standard Actions. Since starting from scratch is not always easy, we’ve made widgets available that you can use directly. Better yet, if you’re a partner, you can even customize them (i.e., remove features, change the order/organization of tabs, buttons, etc.)!

In this blog post, we’ll go through the interface possibilities offered by 4D Write Pro.


4D Write Pro: WP commands and beyond

We’ve received comments on the forum and TAOW about features that previously existed in the 4D Write plug-in but seem to be missing in 4D Write Pro. Yet, they’ve been available for a long time!

In this blog post, we’ll go through a list of existing abilities in 4D Write Pro that seem to have gone unnoticed. In another words, 4D Write Pro features you didn’t know existed.

After all, 4D Write Pro is not limited to WP commands!


A component to export the structure file

Thanks to 4D v17 R3, you can export your structure file in multiple text files. For example, with only a few lines of code you can create a copy of your database every morning. You can use this to keep track of the history or to send your database to a colleague and see the changes when they’re done working on it.

We provide you a ready-to-use component with only two methods: one to configure the data to be exported, and the other to export your database.


Migrate 4D Write documents stored in picture fields

4D Write Pro has become a mature product with a lot of functionalities, surpassing the 4D Write plug-in in many areas (tables and bookmarks, for example). Furthermore, 4D Write Pro is 64-bits compliant, which is great since most operating systems will soon be 64-bits only. Migrating your documents from 4D Write to 4D Write Pro is a “must do”. In order to help you and your customers’ migrations, we’ve simplified the migration process with a ready-to-use component!


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.


What are transactions and how do I use them?

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.


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.

Page 8 of 12