Connect LibreOffice Base to the JET endpoint — native SDBC or JDBC, tables, forms, reports, and DDL
LibreOffice Base connects to the JET endpoint using either its built-in PostgreSQL SDBC driver (libpq-based, no Java needed) or JDBC (with the PostgreSQL driver JAR on the classpath). The native driver is simpler — no JAR files, no classpath configuration. Both methods support extended query protocol and full DDL (CREATE/ALTER/DROP TABLE).
The JET server runs on a Windows machine (the Access engine requires Windows COM/DAO). LibreOffice Base can run on any platform — Windows, macOS, or Linux — connecting to the JET server over the network (or localhost:9432 if running on the same machine). The setup steps are identical across all platforms.
0.0.0.0:9432). See the server README for installation and startup instructions.libreoffice-sdbc-postgresql (installed by default with LO Base on Ubuntu; on Windows, LO Base includes it automatically).
The steps are identical on Windows, macOS, and Linux. The same native PostgreSQL connector is available on all platforms.
Linux: libreoffice --base from terminal, or launch from app menu.
Windows: Start LibreOffice, then File → New → Database.
The Database Wizard appears.
In the Database Wizard:
You can either fill in the fields or use a connection string. The connection string method is simpler for non-standard ports and database paths:
Option A — Connection string (recommended):
Select "Connect directly" and enter:
dbname=C:/Users/ronoh/PowerBI.accdb host=localhost port=9432
Option B — Fill in fields:
C:/Users/ronoh/PowerBI.accdblocalhost9432 (default is 5432 — change it)localhost. If connecting from another machine, use the Windows host's IP address or hostname.
Click "Test Connection". LO Base prompts for credentials:
adminpassword)Expected: "The connection was established successfully."
Click Next →, choose "Yes, register the database for me", then Finish. Save the .odb file (e.g. ~/Documents/PowerBI.odb on Linux, Documents\PowerBI.odb on Windows).
Click the Tables icon in the left sidebar. The 13 tables from PowerBI.accdb should appear: bi_date, bi_manufacturer, bi_product, bi_sales, bi_customer, etc.
Double-click any table to open it in data view.
The libpq-style connection string format used by LO Base's native PostgreSQL driver:
dbname=C:/Users/ronoh/PowerBI.accdb host=localhost port=9432
Key parameters:
dbname — full Windows path to the .accdb file (the JET server resolves this on the Windows host)host — localhost (or VM IP if not using port-forwarding)port — 9432 (JET endpoint default)admin / any non-empty password (prompted at connection time)Both connection methods now work with the JET endpoint:
libpq internally. No Java, no JAR files, no extra configuration. Accepts the database path directly: dbname=C:/Users/ronoh/PowerBI.accdb host=localhost port=9432. The native driver speaks both simple and extended query protocol.postgresql-42.x.jar on the classpath. The JDBC Datasource URL is: jdbc:postgresql://localhost:9432/C%3A%2FUsers%2Fronoh%2FPowerBI.accdb. Extended query protocol is supported — preferQueryMode=extended is now the default.Ensure the JET server is running on the Windows host. Check the server console for JET endpoint listening on 0.0.0.0:9432. From a remote client, verify the network path — the host must be reachable and the port open.
Try 127.0.0.1 instead of localhost if IPv6 resolution is interfering. If connecting over a network, verify the Windows firewall allows inbound traffic on port 9432.
Check the server log on the Windows host for errors. If the server is running but no tables appear, go to View → Refresh Tables in LO Base. Verify pg_class queries are returning rows in the server log.
If the connection fails during TLS negotiation, the native driver may be attempting SSL when the server expects plain. The JET server accepts both — try reconnecting. The native driver typically negotiates this automatically.
accept_all authentication — any user can query or modify any table.