Project databases and components

Since the delivery of 4D v18, a series of blog posts on how to convert and develop with project databases have been published. What about components? This blog post answers that question.

Development and deployment

It’s very simple, the development and the installation of components haven’t changed. You can continue to use the same techniques as before.

Don’t forget, as explained in the blog post on the architecture of project databases, the equivalent of the structure file (.4db) is the “Project” folder. You simply add your component in a “Component” folder next to the Project folder.

Mix project and binary databases?

If you convert your binary database to a project, you don’t need to convert all of your components to projects, too. Like a binary database (.4db), a project database can load both project and binary components.

So you can easily convert your databases and components, one by one.

What’s what?

You have two new database parameters at your disposal to let you to determine:

  • if the host database is a project

$isProject:=Get database parameter(Is host database a project)

  • if the current database is a project

$isProject:=Get database parameter(Is current database a project)

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.