“We can’t install the 64‑bit version of Office because we found the following 32‑bit programs on your PC…” This means that if you have 32‑bit version of Office 2016 on the machine, you will not be able to install 64‑bit Access 2016 components, which is pretty bad for the SSMA (we want to run 64‑bit, remember?). All this looks fairly simple so far, but here comes the first caveat: you can only have one flavor of Office installed at the same time for the same version. We strongly advise to use 64‑bit flavor simply because you can quickly run out of memory while using 32‑bit SSMA with a decent sized database. Whichever option you prefer – make sure to pick the right platform architecture. This has all needed components as well, but it is only available for Access 2010, as of now. Microsoft Access Database Engine 2010 Redistributable.
Or you can get a smaller Microsoft Access Database Engine Redistributable package: Ideally you would just install Microsoft Access Runtime redistributable from one of the following links: The question now is where do I get these… Although it’s pretty straight forward, there are some caveats. Given this, all you need to be able to load Access databases in SSMA is: This wrapper is implemented by managed Primary Interop Assembly (PIA). managed code) – it needs a managed wrapper, that simplifies interaction with the COM component. “Retrieving the COM class factory for component with CLSID. The typical error message that you will get in SSMA, if required components are missing will look like this: We often receive questions about what is really needed to work with Access databases in SQL Server Migration Assistants (SSMA) for Access, so I thought I’ll do a quick run through what is actually required.