Infrastructure and Environment Setup Guide

General recommendation for setting up GeoDin in your network environment

1. System Requirements

Operating System: Windows 10/11 64-bit

Database Clients or DLLs 64-bit (depending on the database used):

  • MS SQL Server: SQL Server Native Client or ODBC driver

  • PostgreSQL: PostgreSQL ODBC driver (psqlODBC)

  • Oracle: Oracle Instant Client

  • Alternatively, the required DLLs can be placed in the GeoDin BIN directory

  • MS Access: Recommended only for single-user environments and smaller projects

2. GeoDin Installation

Install GeoDin using the provided setup. Choose between the following options:

  • Client Installation (standard installation)

  • Network Installation (installation in a UNC path)

Network Installation

If GeoDin is used by multiple users within a network, it is recommended to install the software on a shared network drive. This offers the following advantages:

  • Centralized Configuration: Everyone accesses the same configuration file (e.g., database connections, dictionaries, GeoDin layouts), which avoids inconsistencies.

  • Simplified Maintenance: Updates and changes only need to be made once.

  • Reduced Administrative Effort: No separate installation required on each client PC.

  • Controllable Access Rights: Access can be specifically managed via the network's file system (e.g., NTFS permissions).


If you need a recommendation based on your requirements, please contact our Client Success Teamenvelope to schedule a consultation.

3. GeoDin Databases

GeoDin uses FireDAC (Fire Data Access Components) to connect to databases. This is a universal framework that enables access to a wide range of databases – locally, remotely, or in the cloud.

Examples:

Microsoft SQL Server

PostgreSQL

Oracle

Azure Cloud (Microsoft SQL Server)

Last updated

Was this helpful?