The PostgreSQL DatabaseEngine for Xbase++

The PostgreSQL DatabaseEngine (PGDBE) now offers a groundbreaking capacity to transition existing flat-file table and index files-based Xbase++ applications to a premier SQL Database Management System, all without any limitations.

Through the hybrid qualities of the PostgreSQL DatabaseEngine, it behaves similarly to DBFDBE, FOXDBE, NTXDBE, and CDXDBE DatabaseEngines when opening or generating tables using standard xBase instructions and functions such as DbUseArea(), DbCreate() or USE. This means that the PostgreSQL DatabaseEngine provides navigational or Index-Sequential-Access to SQL Data.

Concurrently, it supports the transparent use of the PostgreSQL Database Management System through SQL commands like SELECT, INSERT, UPDATE or DELETE. This results in zero restrictions for Xbase++ applications developed using SQL as the sole data access and manipulation method. This feature also enables the combination of the two different access methods, which aids in the extension of existing navigational data access-based applications making use of the PostgreSQL ISAM emulation. In fact, it even allows for the addition of SQL query capabilities in a phased manner to boost performance of existing ISAM code.

  Seamless Migration: PGDBE allows Xbase++ applications to be moved to a leading SQL Database Management System without any restrictions, making the transition from ISAM to SQL DBMS easier.

  Hybrid Access: It supports both navigational or Index-Sequential-Access to SQL Data (similar to ISAM) and standard SQL commands, providing flexibility in data access and manipulation.

  Ease of Development: Developers can continue using familiar navigational commands and functions or opt for SQL data access methods, suiting different levels of knowledge and preferences.

  Gradual Enhancement: It supports a step-by-step enhancement of existing navigational data access-based applications by adding SQL query capabilities to increase performance.

  Interoperability: The two data access methods do not interfere with each other and can be mixed as required, allowing for a blend of development teams with varied expertise.