Color scheme: Dark
You are here: start » en » Documentation » Microsoft Access development tools » WKL Bootstrapper » How-to guides » How to: Deliver an Access application to 32-bit and 64-bit Office

How to: Deliver an Access application to 32-bit and 64-bit Office

Deliver one application to users whose Office is partly 32-bit and partly 64-bit.

Requires WKL Bootstrapper 1.0.

Solution overview

The starter is one 32-bit EXE for both: it starts Access as a separate process and reads the bitness from the installed MSACCESS.EXE. Everything the application loads into Access must have the bitness of Access:

PartFollowsWhat to deliver
The starter (Wkl.Bootstrapper.exe)nothing - one EXEOne file for every PC
ACCDEthe Access it was made inOne per bitness, each in a source folder of its own
ACCDB-One file; it runs in both bitnesses
WKL componentsthe bitness of AccessBoth folders, components\x86 and components\x64; the starter registers the matching one
.NET 10 Desktop Runtimethe bitness of Accessx86 for 32-bit Office, x64 for 64-bit Office (installed by IT, for the computer)
ODBC driversthe bitness of AccessThe driver in the bitness of Access

Implementation

  1. Build an ACCDE per bitness - the build tool in a 32-bit Office produces bitness: x86 in app-manifest.json, in a 64-bit Office x64. An ACCDB gets any and needs no second build.
  2. Deliver to two folders, for example \\server\apps\Customers\x86 and \\server\apps\Customers\x64, each with its database, app-manifest.json and both component folders.
  3. Give each group of PCs its starter: the same EXE, a bootstrapper.json whose source names the folder of their bitness. With an ACCDB one starter and one folder serve everybody.
  4. Check on one PC of each kind: Wkl.Bootstrapper.exe /diagnose names the Access it found (“Full x86 …” or “Full x64 …”) and ends with 0 Ok.

Remarks

en/wiki/msaccess/bootstrapper/how-to/install-for-32-and-64-bit-office.txt · Last modified: by Wolfgang van der Stille