> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v7/connectors-and-providers/running-microsoft-access-database-engine-with-astera.md). # Running Microsoft Access Database Engine with Astera If you have a 32-bit Astera Client running on a machine and would like to use the *Microsoft Access Database Engine* provider as a data source, you will need to have the corresponding 32-bit version of it installed on the machine as well. The problem arises when a 64-bit version of *Microsoft Access Database Engine* is already installed on the machine, and a 32-bit version is needed by Astera. Microsoft does not permit installation of both 32-bit and 64-bit by default, but it can be done with a workaround. Microsoft has released the installers [here](https://www.microsoft.com/en-us/download/details.aspx?id=13255). To install the driver required you would need to run it with the “/passive” argument specified. If you have a 32-bit Astera Client and have a 64-bit Microsoft Access driver installed, you will need to install the 32-bit driver version: ***AccessDatabaseEngine.exe /passive*** If you have a 64-bit Astera Client and have a 32-bit Microsoft Access driver installed, you will need to install the 64-bit driver version: ***AccessDatabaseEngine\_X64.exe /passive*** Please try uninstalling either version (e.g. 32 bit or 64 bit) after you have both versions installed. You will get into an error. {% hint style="info" %} **Note**: You will have this error from either version (e.g. 32 bit or 64 bit) when both versions are installed. {% endhint %} The workaround is to run the setup with the /extract switch first. This extracts it to a temp folder. Then right-click on it and select *Uninstall* from the context menu. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.astera.com/astera-data-stack-v7/connectors-and-providers/running-microsoft-access-database-engine-with-astera.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.