Author: Vanessa Talbot

Vanessa Talbot
• Product Owner •Vanessa Talbot joined 4D Program team in June, 2014. As a Product Owner, she is in charge of writing the user stories then translating it to functional specifications. Her role is also to make sure that the feature implementation delivered is meeting the customer need.Since her arrival, she has worked to define key features in 4D. She has worked on most of preemptive multi-threading new features and also on a very complex subject: the new architecture for engined application. Vanessa has a degree from Telecom Saint-Etienne. She began her career at the Criminal Research Institute as a developer for the audiovisual department. She has also worked in media and medical fields as expert in technical support, production as well as documenting new features.
Tips blank

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 blank

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.