Solves the issue great, if not, continue to step 2. Install the Microsoft Access Database Engine 2010 Redistributableįirst, this installation is available at:Īfter the installation has complete, try running you application, if this In order to use the '.12.0' provider you must Resolve you issue you should install the following packages on your If you have built your project under x86 platform, then in order to The first thing you need to check is your build configuration of your application. Which contains the " .15.0"Īnd Office 2016 c:\Program Files\Microsoft Office\root\VFS\ProgramFilesCommonX64\Microsoft Shared\OFFICE16\Csi.dllĬ:\Program Files\Microsoft Office\root\VFS\ProgramFilesCommonX86\Microsoft Shared\OFFICE16\Csi.dll The Office 2013 comes also with csi.dll c:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Csi.dllĬ:\Program Files\Common Files\Microsoft Shared\OFFICE15\Csi.dll
Strings.exe -u -n 10 "c:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\MSO.DLL" | findstr "ACE.O"Įven in the upcoming office 2016 c:\Program Files\Microsoft Office\root\VFS\ProgramFilesCommonX64\Microsoft Shared\OFFICE16\MSO.DLLĬ:\Program Files\Microsoft Office\root\VFS\ProgramFilesCommonX86\Microsoft Shared\OFFICE16\MSO.DLL Strings.exe -u -n 10 "c:\Program Files (x86)\Common Files\microsoft shared\OFFICE14\MSO.DLL" | findstr "ACE.O" on a 64bit System with 32bit drivers installed strings.exe -u -n 10 "c:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL" | findstr "ACE.O" depending on your application architecture choose the appropriate runtime engine (32/64) 6Ĭheck your providers with the powershell-command from both 32 and 64bit shell: (New-Object ).GetElements() | select SOURCES_NAME, SOURCES_DESCRIPTIONĪnd you will see which provider your system can useĮg.all offices from 2007-2016 contain the provider ".12.0".Depending on the app(32/64bit) using the connection you could just install
0 kommentar(er)
