How to integrate Neo4j with MS Access

Learn how to quickly and efficiently connect Neo4j with MS Access for smooth data access.

Read and write Neo4j data effortlessly. Query, integrate, and manage nodes, relationships, and graph data — almost no coding required. You can do it all using the high-performance Neo4j ODBC Driver for MS Access (often referred to as the Neo4j Connector). We'll walk you through the entire setup.

Ready to dive in? Download the product to jump right in, or follow the step-by-step guide below to see how it works.

Neo4j ODBC Driver Powering this integration

High performance
Bidirectional
Low-code / No-code
Easy to use

Built on the ZappySys JDBC Bridge Driver, the Neo4j ODBC Driver is a high-performance, low-code / no-code solution. It enables you to connect to Neo4j data without any coding right in your SQL Server, or any ODBC/JDBC application. Part of the ODBC PowerPack.

Documentation

Prerequisites

Before we begin, make sure you meet the following prerequisite: Java Runtime Environment (JRE) or Java Development Kit (JDK) must be installed on your system.

Minimum required version: Java 17
- Amazon Corretto 17
- Oracle JRE 17
Recommended Java version: Java 21
- Amazon Corretto 21
- Oracle JRE 21

If your JDBC Driver targets a different Java version (e.g., 11 / 17 / 21), install the corresponding or newer Java version.

If you already have a JRE installed, you can try using it too. However, if you experience any issues, we recommend using one of the distributions mentioned above (you can install an additional JRE next to the existing one; just don't forget to configure the default Java in the Windows Environment Variables).

Download Neo4j JDBC driver

To connect to Neo4j in , you will have to download JDBC driver for it, which we will use in later steps. Let's perform these little steps right away:

Visit MVN Repository.
Download the JDBC driver, and save it locally, e.g. to E:\Drivers\JDBC\neo4j-jdbc-full-bundle.jar.
Done! That was easy, wasn't it? Let's proceed to the next step.

Create data source using Neo4j ODBC Driver

Step-by-step instructions

To get data from Neo4j using MS Access, we first need to create an ODBC data source. We will later read this data in MS Access. Perform these steps:

Download and install ODBC PowerPack (if you haven't already).
Search for odbc and open the ODBC Data Sources (64-bit):
Create a User data source (User DSN) based on the ZappySys JDBC Bridge Driver driver:

ZappySys JDBC Bridge Driver
- Create and use a User DSN if the client application runs under a User Account. This is the ideal option at design time (e.g., when developing in Visual Studio). Use it for both types of applications (64-bit and 32-bit).
- Create and use a System DSN if the client application runs under a System Account (e.g., as a Windows Service). This is usually the required option in a production environment. If your Windows Service is a 32-bit application, you must use the 32-bit ODBC Data Source Administrator to configure this
Now, we need to configure the JDBC connection in the new ODBC data source. Simply enter the Connection string, credentials, configure other settings, and then click Test Connection button to test the connection:

Neo4jDSN

jdbc:neo4j://neo4j-instance-host-name:7687?enableSQLTranslation=true

E:\Drivers\JDBC\neo4j-jdbc-full-bundle.jar

neo4j

***************

[]

For Non-SSL Connection (SQL queries), use these values when setting parameters:
- Connection string: jdbc:neo4j://neo4j-instance-host-name:7687?enableSQLTranslation=true
- JDBC driver file(s): E:\Drivers\JDBC\neo4j-jdbc-full-bundle.jar
- User name: neo4j
- User password: ***************
- Connection parameters: []
  Use enableSQLTranslation=true attribute in the connection string to query Neo4j database using SQL queries, e.g.:
```
SELECT * FROM Movie
```
For Non-SSL Connection (Cypher queries), use these values when setting parameters:
- Connection string: jdbc:neo4j://neo4j-instance-host-name:7687
  Excluding enableSQLTranslation=true from the connection allows you to query Neo4j database using Cypher queries, e.g.:
```
MATCH (m:Movie) RETURN m.title AS Movie
```
For SSL Connection (SQL queries), use these values when setting parameters:
- Connection string: jdbc:neo4j+s://neo4j-instance-host-name:7687?enableSQLTranslation=true
For SSL Connection (Cypher queries), use these values when setting parameters:
- Connection string: jdbc:neo4j+s://neo4j-instance-host-name:7687
For Neo4j AuraDB Connection (SQL queries), use these values when setting parameters:
- Connection string: jdbc:neo4j+s://1234abcd.databases.neo4j.io?enableSQLTranslation=true
For Neo4j Aura Connection (Cypher queries), use these values when setting parameters:
- Connection string: jdbc:neo4j+s://1234abcd.databases.neo4j.io
You should see a message saying that connection test is successful:

Otherwise, if you are getting an error, check out our Community for troubleshooting tips.
We are at the point where we can preview a SQL query. For more SQL query examples visit JDBC Bridge documentation:
Neo4jDSN
```
SELECT * FROM Movie
```
```
SELECT * FROM Movie
```
You can also click on the <Select Table> dropdown and select a table from the list.

The ZappySys JDBC Bridge Driver acts as a transparent intermediary, passing SQL queries directly to the JDBC driver, which then handles the query execution. This means the Bridge Driver simply relays the SQL query without altering it.

Some JDBC drivers don't support INSERT/UPDATE/DELETE statements, so you may get an error saying "action is not supported" or a similar one. Please, be aware, this is not the limitation of ZappySys JDBC Bridge Driver, but is a limitation of the specific JDBC driver you are using.
Click OK to finish creating the data source.

Video Tutorial

Read data in Microsoft Access from the ODBC data source

First of all, open MS Access and create a new MS Access database.
In the next step, start loading ODBC data source we created:
Then click next until data source selection window appears. Select the data source we created in one of the previous steps and hit OK:

Neo4jDSN
Continue with tables and views selection. You can extract multiple tables or views:
Finally, wait while data is being loaded and once done you should see a similar view:

Using Linked Table for Live Data (Slow)

Linked tables in Microsoft Access are crucial for online databases because they enable real-time access to centralized data, support scalability, facilitate collaboration, enhance data security, ease maintenance tasks, and allow integration with external systems. They provide a flexible and efficient way to work with data stored in online databases, promoting cross-platform compatibility and reducing the need for data duplication.

Real-Time Data Access:
Access can interact directly with live data in online databases, ensuring that users always work with the most up-to-date information.
Centralized Data Management:
Online databases serve as a centralized repository, enabling efficient management of data from various locations.
Ease of Maintenance:
Updates or modifications to the online database structure are automatically reflected in Access, streamlining maintenance tasks.
Adaptability to Changing Requirements:
Linked tables provide flexibility, allowing easy adaptation to changing data storage needs or migration to different online database systems.

Let's create the linked table.

Launch Microsoft Access and open the database where you want to create the linked table.
Go to the "External Data" tab on the Ribbon. >> "New Data Source" >> "From Other Sources" >> "ODBC Database"
Select the option "Link to Data Source by creating a linked table:
Continue by clicking 'Next' until the Data Source Selection window appears. Navigate to the Machine Data Source tab and select the desired data source established in one of the earlier steps. Click 'OK' to confirm your selection.

Neo4jDSN
Proceed to the selection of Tables and Views. You have the option to extract multiple tables or views:
When prompted to select Unique Key column DO NOT select any column(s) and just click OK:
Finally, Simply double-click the newly created Linked Table to load the data:

Guide to Effectively Addressing Known Issues

Discover effective strategies to address known issues efficiently in this guide. Get solutions and practical tips to streamline troubleshooting and enhance system performance, ensuring a smoother user experience.

Fewer Rows Imported

The reason for this is that MS Access has a default query timeout of 60 seconds, which means it stops fetching data if the query takes longer than that. As a result, only a limited number of rows are fetched within this time frame.

To address this, we can adjust the Query Timeout by following the steps below.

The path may vary depending on the MS Access bitness, such as 32-bit versus 64-bit.

\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\ODBC

\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Jet\4.0\Engines\ODBC

\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\Office\16.0\Access Connectivity Engine\Engines\ODBC

We can identify this issue by examining the Fiddler Log, as MS Access doesn't display any error regarding partial import, which is quite unusual

Please refer to this link : How to use Fiddler to analyze HTTP web requests

#Deleted word appears for column value in MS Access for Linked Table mode

If you used Linked Table mode to get external data and it shows #deleted word rather than actual value for column after you open then most likely its following issue.

Make sure to re-create Linked Table and DO NOT select any key column when prompted (Just click OK)
How to Fix

Table Selection UI Opening Delays

The Table selection UI takes a significant amount of time to open after clicking the 'New Data Source' -> 'Other Data Sources' -> 'ODBC'

The reason for this issue is that MS Access sends a dummy query, leading to several unnecessary pagination cycles before an error is thrown. To mitigate this, we can prevent wasted cycles by configuring the 'Throw error if no match' setting on the Filter Options Tab.

Enhancing Performance through Metadata Addition (Reduces Query Time)

We can optimize query performance by creating Virtual Tables (i.e. views with custom SQL) on Datasource and incorporating META=static columns. Learn how to capture static metadata in this guide.
Performance Options - Generate Metadata Manually

Execute the query initially, save the metadata by selecting 'Save to Meta' (choose Compact Format), and then click 'Save to Clipboard.' Utilize the resulting list by pasting it into the META attribute as follows: 'META=paste here.'

SELECT * FROM products
    WITH(
        META='id:String(20); title:String(100);  description:String(500);'
    )

Optimize Workflow with Automated Import

Employ Automated Import when Linked Tables are not feasible, and we need to depend on Imported Tables with static data.

While using Linked Tables sometime it encounter errors, and we are left with no alternative but to utilize Imported Tables, Automatic Refresh becomes crucial in such scenarios.

Here's a guide on automating refreshes. We can set up automatic refresh on different events, such as when the database opens, a form is opened, or a button is clicked.

To initiate the import process, follow these steps:

Perform the data import using the standard manual steps.
In the final step, we'll encounter a checkbox labeled 'Save Import Steps.' Ensure to check this option.
After saving the steps, we can locate their name in the Save Imports UI. Identify the name associated with the saved steps.
"Now, we can execute the code as shown below:"

Private Sub cmdYes_Click()
    Label0.Visible = True
    DoCmd.RunSavedImportExport "Import-DATA.products"
    Label0.Visible = False
End Sub

Optional: Centralized data access via ZappySys Data Gateway

In some situations, you may need to provide Neo4j data access to multiple users or services. Configuring the data source on a Data Gateway creates a single, centralized connection point for this purpose.

This configuration provides two primary advantages:

Centralized data access
The data source is configured once on the gateway, eliminating the need to set it up individually on each user's machine or application. This significantly simplifies the management process.
Centralized access control
Since all connections route through the gateway, access can be governed or revoked from a single location for all users.

	Data Gateway	Local ODBC data source
Simple configuration
Installation	Single machine	Per machine
Connectivity	Local and remote	Local only
Connections limit	Limited by License	Unlimited
Central data access
Central access control
More flexible cost

To achieve this, you must first create a data source in the Data Gateway (server-side) and then create an ODBC data source in MS Access (client-side) to connect to it.

Let's not wait and get going!

Create Neo4j data source in the gateway

In this section we will create a data source for Neo4j in the Data Gateway. Let's follow these steps to accomplish that:

Search for gateway in the Windows Start Menu and open ZappySys Data Gateway Configuration:
Go to the Users tab and follow these steps to add a Data Gateway user:
- Click the Add button
- In the Login field enter a username, e.g., john
- Then enter a Password
- Check the Is Administrator checkbox
- Click OK to save
Now we are ready to add a data source:
- Click the Add button
- Give the Data source a name (have it handy for later)
- Then select Native - ZappySys JDBC Bridge Driver
- Finally, click OK
Neo4jDSN

ZappySys JDBC Bridge Driver
When the ZappySys JDBC Bridge Driver configuration window opens, go back to ODBC Data Source Administrator where you already have the Neo4j ODBC data source created and configured, and follow these steps on how to Import data source configuration into the Gateway:
- Open ODBC data source configuration and click Copy settings:
  
  ZappySys JDBC Bridge Driver - Configuration [Version: 2.0.1.10418]
  
  ZappySys JDBC Bridge Driver - Neo4j
  
  Read and write Neo4j data effortlessly. Query, integrate, and manage nodes, relationships, and graph data — almost no coding required.
  
  Neo4jDSN
- The window opens, telling us the connection string was successfully copied to the clipboard:
- Then go to Data Gateway configuration and in data source configuration window click Load settings:
  
  Neo4jDSN
  
  ZappySys JDBC Bridge Driver - Configuration [Version: 2.0.1.10418]
  
  ZappySys JDBC Bridge Driver - Neo4j
  
  Read and write Neo4j data effortlessly. Query, integrate, and manage nodes, relationships, and graph data — almost no coding required.
  
  Neo4jDSN
- Once a window opens, just paste the settings by pressing CTRL+V or by clicking right mouse button and then Paste option.
Once done, go to the Network Settings tab and Add a firewall rule for inbound traffic:
- This will initially allow all inbound traffic.
- Click Edit IP filters to restrict access to specific IP addresses or ranges.
Crucial Step: After creating or modifying the data source, you must:
- Click the Save button to persist your changes.
- Hit Yes when prompted to restart the Data Gateway service.
This ensures all changes are properly applied:

Skipping this step may cause the new settings to fail, preventing you from connecting to the data source.

Create ODBC data source to connect to the gateway

In this part we will create an ODBC data source to connect to the ZappySys Data Gateway from MS Access. To achieve that, let's perform these steps:

Search for odbc and open the ODBC Data Sources (64-bit):
Create a User data source (User DSN) based on the ODBC Driver 17 for SQL Server driver:

ODBC Driver 17 for SQL Server

If you don't see the ODBC Driver 17 for SQL Server driver in the list, choose a similar version.
Then set a Name for the data source (e.g. Gateway) and the address of the Data Gateway:

ZappySysGatewayDSN

localhost,5000

Make sure you separate the hostname and port with a comma, e.g. localhost,5000.
Proceed with the authentication part:
- Select SQL Server authentication
- In the Login ID field enter the user name you created in the Data Gateway, e.g., john
- Set Password to the one you configured in the Data Gateway
Then set the default database property to Neo4jDSN (the one we used in the Data Gateway):

Neo4jDSN

Neo4jDSN

Make sure to type the data source name manually or copy/paste it directly into the field. Using the dropdown might fail because the Trust server certificate option is not enabled yet (next step).
Continue by checking the Trust server certificate option:
Once you do that, test the connection:
If the connection is successful, everything is good:
Done!

We are ready to move to the final step. Let's do it!

Access data in MS Access via the gateway

Finally, we are ready to read data from Neo4j in MS Access via the Data Gateway. Follow these final steps:

Go back to MS Access.
First of all, open MS Access and create a new MS Access database.
In the next step, start loading ODBC data source we created:
Then click next until data source selection window appears. Select the data source we created in one of the previous steps and hit OK:

ZappySysGatewayDSN
Read the data the same way we discussed at the beginning of this article.
That's it!

Now you can connect to Neo4j data in MS Access via the Data Gateway.

If you are asked for authentication details, use Database authentication, SQL authentication or Basic authentication option and enter the credentials you used when configuring the Data Gateway, e.g. john and your password.

Troubleshooters & resources (JDBC Bridge Driver)

Below are some useful community articles to help you troubleshoot and configure the ZappySys JDBC Bridge Driver:

How to combine multiple JAR files
Learn how to merge multiple .jar dependencies when your JDBC driver requires more than one file.
How to fix JBR error: “Data lake is not available / Unable to verify trust for server certificate chain”
Resolve SSL or certificate validation issues encountered during JDBC connections.
System Exception: “Java is not installed or not accessible”
Fix Java path or environment issues that prevent the JDBC Bridge from launching Java.
JDBC Bridge Driver disconnect from Java host error
Troubleshoot unexpected disconnection problems between SSIS and the Java process.
Error: Could not open jvm.cfg while using JDBC Bridge Driver
Resolve JVM configuration path errors during driver initialization.
How to enable JDBC Bridge Driver logging
Enable detailed driver logging for better visibility during troubleshooting.
How to pass JDBC connection parameters (not by URL)
Learn how to specify connection properties programmatically instead of embedding them in the JDBC URL.
How to fix JDBC Bridge error: “No connection could be made because the target machine actively refused it”
Troubleshoot firewall or local port binding issues preventing communication with the Java host.
How to use JDBC Bridge options (System Property for Java command line, e.g., classpath, proxy)
Configure custom Java options like classpath and proxy using JDBC Bridge system properties.

Conclusion

In this article we showed you how to connect to Neo4j in MS Access and integrate data without writing complex code — all of this was powered by Neo4j ODBC Driver. It's worth noting that ZappySys JDBC Bridge Driver allows you to connect not only to Neo4j, but to any Java application that supports JDBC (just use a different JDBC driver and configure it appropriately).

Download ODBC PowerPack now or ping us via chat if you have any questions or are looking for a specific feature (you can also reach out to us by submitting a ticket):

Download Chat