Convert PostgreSQL to Access.

Our DBConvert/DBSync cross database migration/sync solutions support data transfer from PostgreSQL to Microsoft Access.

Our software is option rich, making all your data exchange jobs between PostgreSQL / Amazon RDS PostgreSQL / Heroku Postgres and Access both fast and fully customized to your needs.

You can specify whether or not to include tables, fields and indices, change data types, and choose subsets of schema objects to migrate.

Integrated Data filters allow extracting specified data only and passing them to target databases smoothly.

PostgreSQL as a server database is used for storing consolidated data in one place on a daily, weekly or monthly basis. But sometimes if there is no way to share this data through the web or the task is rather to provide partial data as per user requirements at a specific time. Using MS Access databases as an intermediate storage node for your clients could be a fitting solution.

 DBConvert for Access & PostgreSQL

Migration directions:

  • Access → PostgreSQL, Dump, PHP Script
  • PostgreSQL → Access
  • Access ↔ Amazon RDS ↔ Heroku Postgres
  • MS Access queries → PostgreSQL views

Version: 4.3.8

Release Date: July 30, 2019

 DBSync for Access & PostgreSQL

Sync directions:

  • MS Access ↔ PostgreSQL
  • Access ↔ Amazon RDS ↔ Heroku Postgres

Version: 4.2.1

Release Date: April 27, 2020

Try All-in-one DB migration and Sync software.

DBConvert Studio

 Version: 1.8.4

Release Date: Nov. 23, 2020

Supported databases:

  • SQL Server
  • MySQL
  • Oracle
  • PostgreSQL
  • Access
  • FoxPro
  • SQLite
  • Firebird
  • Excel
  • IBM DB2
  • Azure SQL
  • Amazon RDS
  • Amazon Aurora
  • Heroku Postgres
  • Google Cloud

Related Links

Supported OS:

Using PostgreSQL to Access conversion and synchronization tools.

When you start DBConvert or DBSync application in GUI mode it guides you through several steps to set up the database migration or synchronization:

1. Connect to PostgreSQL source database.

If a source database requires you to log in, you can specify a user name/ password and host/ port parameters.

Connect to PostgreSQL source database from DBConvert

2. Connect to Access destination database.

Specifying parameters for destination database looks like the same as for source. Usually, it consists of defining connection settings and username/password pairs.

Connect to Access target database from DBConvert

NOTE #1: Every DBConvert or DBSync tool has two different databases in its name. That means any specified database from a pair can be set up as a source or destination. Besides, the same type of database may be set up both as a source or destination.

As an example, here is the list of possible migration directions with on-premises databases:

  • PostgreSQL to Access
  • Access to PostgreSQL
  • PostgreSQL to PostgreSQL
  • Access to Access

NOTE #2: Don't be confused by the fact that connections to cloud databases like Amazon RDS, Microsoft Azure SQL, Google Cloud, and Heroku are not explicitly specified in the configuration of a source or destination in the DBConvert / DBSync interface. To connect to Cloud database instances, use the same settings as you do for traditional on-premises databases.

NOTE #3: Your connections to source and target databases stay active until you close DBConvert/ DBSync application or reopen new connections on "source" and "destination" steps.

Read more about the specific source/ destination configurations for different databases.

3. Custoimzation and configuration.

At the next step, you can specify precisely which tables, fields, indices, views you want to transfer to the Access destination database. Just check/ uncheck the box in front of each database object you want to convert.

Customize general database/ tables settings. Or set up a particular table , field, index individually when migrating data from PostgreSQL to Access.

Check out our articles about Custoimzation and configuration. for detailed information.

The screenshot below sums up general features available in DBConvert software solutions.

4. Detection of potential database migration issues. Errors and Warnings

The database typically constrains certain relations on the data that cannot be violated. On the customization step, a smart error checker verifies all possible Data integrity and Referential integrity issues and highlights them, if any, before performing a migration.

DBConvert software to default tries to automatically map database types from the source PostgreSQL database to the closest equivalent of the target Access database types. But you can manually change data types for the whole database globally with "Global mapping" or individually for each field.

Check out Smart error checker. Errors and Warnings for more information.

5. Execution. The final stage of data migration from PostgreSQL to Access

Once you configure source and destination databases for migration in the previous steps, you can start the actual conversion or synchronization process.

Click the "Commit" button to start conversion. Also, here, you can monitor the migtation/ synchronization process.

Optionally save connection settings and configuration parameters into the session file to schedule the launching of sync or migration jobs regularly.

Execution step of DBConvert products

Read more about execution stage available options.

Command line mode

Previously saved sessions can be passed as parameters to Command-Line DBConvert Client. A session keeps PostgreSQL source and Access target database connection settings with other specified options.

Example: C:\Program Files\DBConvert\access2postgresqlPro\access2postgresqlPro_Cons.exe /Session:"Session_Name"

NOTE: First, you have to run the software in GUI mode to create a session file with initial parameters.

Built-in scheduler.

Our applications come with a built-in scheduler to run database migration and sync jobs at specified times. Just set the scheduled date and time to execute job sessions automatically.

DBConvert screenshot

Highlights

Requirements

  • Microsoft Visual C++ 2008 x86 Redistributable package
  • Necessary privileges to write into database on the target PostgreSQL server (this requirement is optional as there is an option to overcome the restrictions using dump file or PHP Script)
  • Access 2000 or higher. Both Access 32/64 versions are supported