---
title: "Network installation of portier® Vision 5 with Firebird"
description: "Firebird 4 on the server, Vision 5 on the workstations, and the connection set in portier Vision Companion."
url: https://help.portiervision.com/en/articles/112-network-installation-of-portierr-vision-5-with-firebird
collection: "Integrations & IT Setup"
updated: 2026-10-15
language: en
alternates: [de, fr]
---

# Network installation of portier® Vision 5 with Firebird

Firebird 4 on the server, Vision 5 on the workstations, and the connection set in portier Vision Companion.

This guide covers portier Vision 5 with Firebird 4. The database sits on a server and every workstation connects to it. Firebird 4 is free of charge.

## Before you start

-   Firebird 4 is installed on the server and running as a service.
    
-   Port 3050 is open in the server firewall.
    
-   You know the path under which the server sees the database file.
    
-   Firebird needs no ODBC driver. That driver is only for Microsoft SQL Server.
    

## 1\. Install Vision on the first workstation

Run the setup. It installs every component, there is no component selection.

The install page carries the checkbox **Install Microsoft ODBC Driver 18 for SQL Server (recommended)**. On a Firebird-only site you can clear it. When in doubt leave it ticked, an unused driver does no harm. Your choice is remembered and also applies to later automatic updates.

## 2\. Move the database to the server

The database file **PORTIERVISION.GDB** sits in the program directory. Move it to the server.

Put the file in a local folder on the server and do not share that folder on the network. Workstations connect through the Firebird service, not through a file share.

## 3\. Set the connection in Companion

You set the database connection in **portier Vision Companion**. You will find it as `portierVisionCompanion.exe` in the Vision program directory.

The first start shows the welcome screen with the language picker. After **Continue** comes the sign-in screen. It carries the note _The database configurator is reachable without signing in_ and below it the button **Open database configurator**. Take that route. Sign-in reads its user records from the very database you are about to configure. Later, in day to day use, the same screen sits on the **Database Configuration** tab.

![Companion sign-in screen with the Open database configurator button](https://staticfiles.gleap.io/p69f19d405a24ffe33e3bc1d5/GCMiGrYiy7s6IMbz6J4L5DNQ0lxo8ATEEvxItnyRy3gO0n7Qj4UTzv1Cntzf27mmdrHahNjNSS6.png)

_Companion sign-in screen with the Open database configurator button_

Under **Database Type** choose **Firebird**, then fill in:

-   **Host**, the server name or IP address
    
-   **Port**, 3050 for Firebird
    
-   **Database Path**, the path to the GDB file as the server sees it, for example `C:\portier\PORTIERVISION.GDB`. **Browse** only helps when you are working on the server itself.
    
-   **Username** and **Password** of the Firebird login
    

![Database configuration with database type Firebird](https://staticfiles.gleap.io/p69f19d405a24ffe33e3bc1d5/HlpkzMsH1ME9rE79bIR00NewDIHVHfP3mZSqP3cJECp926FnqfmNvBXfJJfUXDvEa8aRJJWyiqx.png)

_Database configuration with database type Firebird_

Click **Test Connection**. On success Companion reports _Connection successful, please save the configuration_. The test on its own saves nothing.

![A successful connection test](https://staticfiles.gleap.io/p69f19d405a24ffe33e3bc1d5/NNxmLcQdzjrhwYufayOhkFO1sus4XXRtrQUEsani2s7YuZc8ex5TAU1K6IbkdqGmlkB6DFJdO3H.png)

_A successful connection test_

Click **Save Config**. Without a prior test Companion asks **Save without testing?** first.

If you were signed in while saving, Companion signs you out. The session belonged to the previous database. Simply sign in again.

Vision and Companion read the same `portiervision.ini` in the program directory. What you save here applies to both.

## 4\. Set up the other workstations

Install Vision on every other workstation. Whether you can then copy the finished `portiervision.ini` across is decided by **Config Encryption** on the same screen.

-   **DPAPI** is the default. _With DPAPI, the config file is locked to your user and machine._ Copying it achieves nothing, so configure each workstation separately in Companion.
    
-   **Shared Key**. _With Shared Key, you can share the config file with others._ Copy the file into the program directory of every other workstation.
    

After switching method, save the configuration again. Otherwise the old encryption stays in place.

![Config Encryption with the choice between Shared Key and DPAPI](https://staticfiles.gleap.io/p69f19d405a24ffe33e3bc1d5/PnKDRs9qMF6FQ0nNvWso0N1HaL2lVsrDrK74j0RL3LkCpxcuDHQGRa7fGbPJ2EKJDx1LY4Nzwwi.png)

_Config Encryption with the choice between Shared Key and DPAPI_

## When the connection fails

-   The database path is the path as the server sees it. Not a mapped drive, not a path from the workstation.
    
-   Is the Firebird service running on the server?
    
-   Is port 3050 open?
    
-   Are the Firebird user and password correct?
    

How many workstations a Firebird site carries, and when Microsoft SQL Server is the better choice, is covered in the system requirements.