Database Tour Documentation Contents Index

Opening PostgreSQL Databases

 

There are several ways to connect PostgreSQL databases in Database Tour:

1. Opening through FD interface. Select FD interface, click PostgreSQL, then fill all needed database parameters. Consult with your database administrator on how to choose correct parameters.

Example of configuring a database connection:

(required parameters are highlighted)

Vendor libraryC:\Program Files (x86)\PostgreSQL\10\bin\libpq.dll
Server200.200.190.222
Port5432
Databasecustomers
CharsetUTF8
Application nameDatabase Tour Pro
User namedexter
Password********
SQL command separator;

2. Opening through connection string. Select ADO interface, then choose Connection string option and write a connection string. This way is very flexible and allows to specify many additional parameters in the connection string and override standard Database Tour connection behavior. It is recommended for advanced users. Here are basic connection strings (more examples and details can be found in the Internet):

Provider=PostgreSQL OLE DB Provider;Data Source=myServerAddress;location=myDataBase;User ID=myUsername;password=myPassword;   (PostgreSQL OLE DB Provider must be installed)

Driver={PostgreSQL};Server=IP address;Port=5432;Database=myDataBase;Uid=myUsername;Pwd=myPassword;   (PostgreSQL ODBC Driver must be installed)

3. Opening through ODBC DSN. Create (if it does not exist yet) an ODBC DSN of the corresponding type using Windows administrative tools, and point it to the database. Then:

- Select FD interface, click ODBC, then point the Data source parameter to the ODBC DSN by selecting it from the drop-down list.

or

- Select ADO or BDE interface, then choose ODBC data source option and then select the needed ODBC DSN from the drop-down list.

Notes

  1. PostgreSQL client must be installed. The bit-version of it (32 or 64) must match the bit-version of the application.
  2. When choosing the ODBC option, please make sure the corresponding ODBC driver installed and the bit-version of it matches the bit-version of the application (32 or 64).

See also

 Examples of ADO Connection Strings