Installation Guide

Prerequisites

• Windows 10/11 or Windows Server 2019+ (64-bit)
• Microsoft Access Database Engine (ACE) — included with Microsoft 365 / Access, or download the free Access Database Engine redistributable
• One or more .accdb or .mdb database files

Running the Installer

The MS Access Endpoint ships as a single MSAccess-Endpoint-0.3.0-setup.exe file — a self-contained 64-bit Windows installer built with Inno Setup. Administrator privileges are required.

⬇ Download Installer

What the Installer Asks

The installer wizard walks through several configuration screens:

What the Installer Does

1. Places files — copies jet-server.exe and supporting files to the install directory.
2. Writes configuration — generates jet-endpoint.toml from your wizard choices and places it in %PROGRAMDATA%\JetEndpoint\. If a config already exists, it is never overwritten — upgrades preserve your settings.
3. Creates runtime directories — logs\ and schema_cache\ under %PROGRAMDATA%\JetEndpoint\.
4. Registers service (if selected) — creates the JETEndpoint Windows Service with auto-start and automatic restart on failure.

Configuration File

All server behaviour is controlled by a single file: jet-endpoint.toml, located in %PROGRAMDATA%\JetEndpoint\ (typically C:\ProgramData\JetEndpoint\). You can edit it with any text editor.

Example Configuration

[network]
port = 9432
max_connections = 255
idle_timeout_seconds = 300
bind_address = "0.0.0.0"

[auth]
mode = "simple"
users = [["admin", "my-secure-password"]]

[debug]
diagnostics = "normal"
log_retention_days = 14
log_msg_max_len = 500

Running the Server

As a Windows Service (recommended for production)

If you selected "Install as Windows Service" during setup, the endpoint runs automatically on boot and restarts on failure. Manage it through services.msc or PowerShell:

sc query JETEndpoint
sc stop JETEndpoint
sc start JETEndpoint

The service logs to the Windows Event Log as source "JETEndpoint" and also writes jet-server.log to the log directory.

Console Mode (for testing)

Run the server directly from a command prompt. Useful for seeing live output during initial setup:

"C:\Program Files\JetEndpoint\jet-server.exe"

Press Ctrl+C to stop. Log output appears in the console window. Console mode reads the same jet-endpoint.toml from %PROGRAMDATA%\JetEndpoint\.

Logging

Logs are written to %PROGRAMDATA%\JetEndpoint\logs\jet-server.log by default. The file is rotated daily or when it exceeds log_max_file_size_mb (default 10 MB). Rotated logs are named jet-server.YYYY-MM-DD.log.

What gets logged depends on the diagnostics setting:

Console mode — port 9432, max 255 connections, idle timeout 300s
JET endpoint listening on 0.0.0.0:9432
Max connections: 255

Connecting

Once the server is running, connect any PostgreSQL-compatible client to the host and port. The "database name" is the full Windows path to your .accdb file:

psql -h localhost -p 9432 -U admin -d "C:/Users/Public/Documents/test.accdb"

From Python:

import pymsaccess
conn = pymsaccess.connect(host="localhost", port=9432, user="admin",
                          dbname="C:/data/mydb.accdb")
cur = conn.cursor()
cur.execute("SELECT * FROM [bi_date]")
for row in cur:
    print(row)

From DBeaver, LibreOffice Base, or any JDBC tool — use the standard PostgreSQL JDBC driver with jdbc:postgresql://host:9432/. DBeaver works with both preferQueryMode=simple and preferQueryMode=extended (recommended for full metadata support).

Troubleshooting