Tips

Binary database vs. Project database

As you know, 4D now supports two ways to work with sources: binary and project databases. Binary databases are the 4D we all know and love, with source code in a binary file to allow team development with 4D Server, and all of the design elements (methods, forms, structure, etc.) gathered in a single, compact binary file, the “.4db” file. Project databases make it easier for distributed teams to work collaboratively by storing the source code in a source control system in separate, plain text files. Projects will not replace the 4DB, we have no plans to make the 4DB disappear. It’s about two different ways of working and developing. It’s up to you to choose what best suits your needs. Here’s a blog post to help you decide:

Tips

Project database: Deploying your application

So your application has been developed and you’re ready for the next step. 4D lets you:

  • generate a compiled database that no longer contains any interpreted code,
  • generate a standalone application that can be double-clicked, (i.e., merged with 4D Volume Desktop, 4D’s database engine),
  • generate client/server applications with automatic updates of client and server parts.

 

With a project database, you can also build your final applications for both platforms. A project database uses the same configuration file as a binary database.

Tips

Project Databases: Post conversion

In this blog post, we showed you how to convert a binary database into a project database. Once everything is ready and the conversion has successfully completed, you can start working with your project database. However, some questions may arise: are all the files in the database useful? It’s obvious that the”.4DB” structure file is no longer needed. Can I delete other files?

Here’s everything you need to know after the conversion.