none
Office 2013 need 32 bits not 64bits RRS feed

  • Question

  • I am receiving the error The Microsoft . ACE OLEDDB.12.0 provider is not registered on the local machine.

    I have 64 bit and need 32 bits on windows 10 is that possible with Microsoft office 2013

    Friday, March 29, 2019 6:16 AM

All replies

  • Hi mf15,

    "Microsoft.ACE.OLEDB.12.0" can’t be used on "x64" platform, so you can try to change the target platform of the project to "x86".

    Regards,

    Kyle


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, March 29, 2019 6:35 AM
    Moderator
  •  

    You cannot install the Microsoft.ACE.OLEDB.12.0 provider with a different processing architecture (bittedness) from your Office install. Well, sort of, you can hack your way around Microsoft's blockade but the side effects makes your program a hard sell to your customers. So practically the version of ACE you can install on a client machine is limited by the client's Office version. 

    That also means you can't target AnyCPU because it would target the OS's CPU architecture which is usually different than the Office architecture (the most common setup is Office 32 bit install on Windows 64 bit). Well, sort of. If you got a lot of free time you can still call NGEN in your installer to precompile your assemblies correctly based on Office version. Or you can simply make two installers and let the customer download the correct version:

    X86 installer for 32 bit Office. Chain install AccessDatabaseEngine.exe.

    X64 installer for 64 bit Office. Chain install AccessDatabaseEngine_x64.exe.



    Visual C++ MVP

    Saturday, March 30, 2019 1:59 AM