Prerequisites

What the server, the workstations, and the database need for Database Gateway to run, broken down by component and with the supported versions.

Server: data service

Item	Requirement
Operating system	64-bit Windows 10 or 11, Windows Server 2016 or later; or Linux (x64) with systemd, as a separate package without an installer—see Set up the service manually as a system service
Permissions to install	administrator (the installer asks through User Account Control)
.NET runtime	not required; the program includes its own runtime
Ports	HTTPS 8433 and HTTP 8434 (on the server itself only); you can change both
Certificate	a server certificate for HTTPS; the installer selects an existing one, obtains one from Let's Encrypt, or creates a self-signed one for testing
IIS	only if the service is to run behind IIS—see Run the service behind IIS or a proxy

Item	Requirement
Database system	Microsoft SQL Server 2016 or later
Compatibility level	100 or higher; the service uses nothing that requires a higher level
Data source login	a SQL Server login or the service account (integrated security) with the permissions that users are meant to exercise through the service
For passing through the person	in addition, permission to impersonate the people's logins—see Pass people's identities through to SQL Server

Application	Requirement
Access (linked tables, pass-through)	Access 2010 or later, or the Access Runtime, 32-bit or 64-bit, with the OData ODBC driver in the same bitness as Office
Excel	Power Query (Microsoft 365, or Excel 2016 and later); no driver required
Power BI Desktop	OData feed; no driver required
Your own programs	HTTP with JSON or XML; for .NET, the .NET client; for VBA, “WklGatewayClient: VBA class for the data service” (documentation of the administration app)

Item	Requirement
Access	Supported: Access from Microsoft 365 or Office LTSC 2024, full version or Runtime, 32-bit and 64-bit. Older versions from Access 2010 on usually work as well, but they aren't acceptance-tested and no longer receive security updates from Microsoft
Driver	OData ODBC driver in the same bitness; it comes with the administration app's delivery, and the starter sets it up per user
Components	WKL Forms Object Library and WKL Office JSON; the delivery brings them in the version the app was built with, and the starter registers them per user, so you don't register anything by hand. See “Set up the administration app on a workstation” (documentation of the administration app)
Sign-in	a personal key or an assigned Windows account with the `admin` right, and an authenticator app: administration always requires the second factor as long as the lower bound `Gateway:Store:RequireAdminTotp` is on (the default)