1. Excel Odbc Driver
2. Office 2016 Data Connectivity Components
3. 64 Bit Database Driver

. This download will install a set of components that facilitate the transfer of data between existing Microsoft Office files such as Microsoft Office Access 2007 (.mdb and.accdb) files and Microsoft Office Excel 2007 (.xls,.xlsx, and.xlsb) files to other data sources such as Microsoft SQL Server. Connectivity to existing text files is also supported. ODBC and OLEDB drivers are installed for application developers to use in developing their applications with connectivity to Office file formats. The 2007 Office System Driver are not intended:. As a general replacement for Jet (If you need a general replacement for Jet you should use ).

If you want to install 64-bit Microsoft Access Database Engine. Compatibility Pack for the 2007 Office system, Microsoft Office Access database engine 2007.

As a replacement for the Jet OLEDB Provider in server-side applications. As a general word processing, spreadsheet or database management system; to be used as a way to create files. (You can use Microsoft Office to create the files that Microsoft Office supports, or use development tools to create Office OpenXML compatible files.). To be used by a system service or server-side program where the code will run under a system account, or will deal with multiple users identities concurrently, or is highly reentrant and expects stateless behavior.

Examples would include a program that is run from task scheduler when no user is logged in, or a program called from server-side web application such as ASP.NET, or a distributed component running under COM+ services. This package contains components that are at the same version as the “The 2007 Microsoft Office Suite Service Pack 1 (SP1)” release. The Office System Drivers are only supported under certain scenarios, including:. Desktop applications which read from and write to various files formats including Microsoft Office Access, Microsoft Office Excel and text files.

1. Learn about the differences between 32-bit and 64-bit software. Using 64-bit Applications with Microsoft Access. New Microsoft ACE (Access Database Engine).
2. On a 64-bit computer, you must. Select Microsoft Office 12.0 Access Database Engine OLE. To connect to data source that uses Access 2007, you cannot select.

To transfer data between supported file formats and a database repository, such as SQL Server. For example, to transfer data from an Excel workbook into SQL Server using the SQL Server Import and Export Wizard or SQL Server Integration Services (provided the SSIS jobs run in the context of a logged-on user with a valid HKEYCURRENTUSER registry hive).

Excel Odbc Driver

Why can't the 32 and 64 bit versions of the Microsoft Access Database Engine 2010 Redistributable (AccessDatabaseEngine.exe and AccessDatabaseEngineX64.exe) both be installed on the same machine? The fact that they cannot forces us to compile two different versions of our application; one specifically for x86 platform and one for x64 platform. Then we have to somehow determine which version of the ACE driver is installed so we know which version (32 or 64 bit) of our application to install. Life would be much simplier if we could just compile our app for the default AnyCPU and then both 32 and 64 dataproviders were allowed to be installed. If they have the 32 bit ACE OleDB dataprovider installed and then try running our app compiled for AnyCPU platform on an 64 bit system then they get the following error when we try to use the following connection string with OleDBConnection; New System.Data.OleDb.OleDbConnection('Provider=Microsoft.ACE.OLEDB.12.0;Data Source=' & clientPathMDB) 'The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.' Again, I know that we can avoid this by targeting our app specifically for x64. But I don't think we should have to.

Why can't 32 and 64 bit ACE coexist? What complicates matters even more is IF they have any other 32 bit Office component installed then they CAN NOT install the 64 bit Access Database Engine 2010 Redistributable (AccessDatabaseEngineX64.exe). So if they cannot coexist then how to we determine which is installed so we know which version of our app to install? It's based upon the fact that Microsoft does not support the side by side install of 32 and 64-bit Microsoft Office 2010 or their dependent components. In addition, Microsoft recommends that, for now, customers use the 32-bit version of Office since many of the common Office Add-ins will not run in the 64-bit Office environment. Seems to me you can handle this in the installer or let the user decide whether to install the 32-bit or 64-bit version (assembly), or maybe both.

Paul Microsoft MVP (Visual Basic). I'm sorry, but that's not a very helpful answer to the question. Q: Why can't the 32 and 64 bit versions of the Microsoft Access Database Engine 2010 Redistributable (AccessDatabaseEngine.exe and AccessDatabaseEngineX64.exe) both be installed on the same machine?

A: Microsoft does not support the side by side install of 32 and 64-bit Microsoft Office 2010. That's not answering, that's just repeating the question in other words. Is there anything in these technologies that prevent MS from supporting 32 and 64-bit drivers side-by-side or did they do it just to make life hard for developers:-) I'm assuming the first but haven't seen anyone from MS explain the underlying reasons for this seemingly arbitrary decision. Q: Why can't I do this?

A: Because we don't support it. Q: Why can't you support it? A: Because we don't support it. Hi, I exactly cant say more on your issue of side-by-side installation of 32 bit and 64 bit packages on windows platform. But would like to point you out concept called as WOW which may create above mentioned issue. Definition: Many Win16 applications can run without changes on 32-bit editions of Windows, complete with the limitations of such applications compared with applications written for Win32.

The operating system thunks 16-bit APIs to their underlying 32-bit equivalents in order to provide support for 16-bit pointers, memory models and address space For details about WOW (Windows On Windows) please refer to url below:. I hope the above listed links can put more light on what Paul Clement is trying to explain. Mesiya songs vol 1. One more thing I would like to point is: while releasing(compiling, building) your binaries please set the target cpu mode as any. So that it becomes less painful (I hope this can answer your other questions).

Please let us know your views on this. Manish Patil Posting is provided AS IS with no warranties, and confers no rights.

This is not just a pain for developers but for any user of an Vista64 or Win7 x64 machine. It makes you wonder why Microsoft came up with this.artificial. limitation/restriction as they are pushing users to move to 64-bit OS's. Now few people will actually use the 64-bit version of Office 2010 as that only brings more problems. However for a lot of other programs it makes sense to run in 64-bit mode on x64 Vista or Win7. However those programs will then require 64-bit Office drivers to use MSOffice files.

The only suggestion I know, is to first install the 64-bit Office 2010 ODBC/OleDB drivers and after that the (32-bit) Office 2007 application suite (or drivers). That does mean that the 32-bit drivers have a different version number than the 64-bit drivers though. If when you are trying to install AccessDatabaseEnginex64.exe you get this message: Open your registry editor and find this key: HKEYCLASSESROOT Installer Products 000000F01FEC Rename 000000F01FEC to.000000F01FEC: HKEYCLASSESROOT Installer Products.000000F01FEC Then try to install again, when done change the key to the original value: HKEYCLASSESROOT Installer Products 000000F01FEC That works for me, now I have 32 and 64 bit versions of Microsoft.ACE.OLEDB provider installed in my server. So effectively you can only have the 32-bit and 64-bit MS Office runtimes on the same machine, if you use different versions. That would most likely be the Office 2007 32-bit application suite and seperately the 64-bit Office 2010 runtime files. Since machines in the average enterprise would come with the Office suite installed by default, the workarounds to get the 64-bit Office 2010 runtimes setup next to an existing (32-bit) installation are very useful.

Still why did Microsoft put these artificial barriers in place? Especially people with a 32-bit Office 2010 application suite will have a problem, as the 32-bit and 64-bit drivers have the same ADO/OleDB/etc. I just recently ran into this situation. Furthermore, EVERY time you run Excel or Word, they also 'reconfigure', and you can no longer create new folders in Outlook (tells you to reinstall Outlook - nice!), and your signon to LIVE says 'Something went wrong.' This thread has been inactive for a while.

Has anyone (i.e. MSFT) come up with someway that I can build a single C# application for CPU=ANY or even CPU=x64 that will work on different x64 machines, one with x86 Office and one with x64 Office? My boss did not read the caveat to use 32 bit Office and neither of us wants to reinstall the other version of Office, that being so much fun.

Thanks, Dave Dave. Setting CPU=ANY does NOT help because if you build CPU=ANY it runs 64-bit on an x64 machine so will not talk to 32-bit Office without the AccessDatabaseEnginex64 drivers, and then Office starts doing weird things. You have to set the /32preferred flag (or whatever it is) and there is no preferred about it since now it always runs 32 bit and won't work on a different machine that has 64-bit Office and the 64-bit drivers. Catch-22 - MSFT did not think this one through. Basically, there is no way to build one C# app that will even run on x64 machines, much less x86 and x64 machines, where one machine has Office 32-bit and another Office 64-bit, w/o Office reconfiguring Word and Excel every invocation, or Outlook able to create new sub folders, or being able to log in to LIVE. Please tell me I'm wrong! Microsoft never intended to support the side by side installation of both 32 and 64-bit versions of Office.

This includes the dependent components, such as the ACE OLEDB Provider. The setup and configuration checks for the Office apps were designed to prevent this. I would suspect that, as with many applications, you will need to deploy two versions of the app, one that targets 32-bit environments and one for 64-bit. In the.NET world that means one configured with the x86 platform option and one for x64 (under Build.Configuration Manager in VS). I don't see this as an issue, because technically you still only have one version of the app. You just generate two different assemblies. Paul Microsoft MVP (Visual Basic).

Office 2016 Data Connectivity Components

Well maybe you don't see this as an issue, but other people do - #1 There is no way to build an x86 and x64 binary at the same time other than a tedious manual process that modifies the solution back and forth. #2 There is no way to have a WIX installer install an x86 or x64 version based on the version of Office installed. #3 This wastes the concept of CPU=ANY. There are lots of issues and problems I'm sure MSFT had no intention of supporting which does not mean they shouldn't when it is a PITA for their users. The Configuration Manger (thx for telling me there was one) does not have a choice that says 'build me two assemblies so that my app can work with either version of Office'. And furthermore, the x64/ANY app will work with the x64 driver and the 32-bit Office data but breaks Office itself so this COULD be made to work, but the real answer is apparently MSFT does not WANT to bother to make it work, all intentions aside.

Here's a workaround for installing the 64-bit version of the Microsoft Access Database Engine 2010 redistributable on a system with a 32-bit MS Office version installed:. Check the 64-bit registry key 'HKEYLOCALMACHINE SOFTWARE Microsoft Office 14.0 Common FilesPaths' before installing the 64-bit version of the Microsoft Access Database Engine 2010 redistributable. If it does not contain the 'mso.dll' registry value, then you will need to rename or delete the value after installing the 64-bit version of the Microsoft Access Database Engine 2010 redistributable on a system with a 32-bit version of MS Office installed. Use the '/passive' command line parameter to install the redistributable, e.g.

'C: directory path AccessDatabaseEnginex64.exe' /passive. Delete or rename the 'mso.dll' registry value, which contains the path to the 64-bit version of MSO.DLL (and should not be used by 32-bit MS Office versions). Now you can start a 32-bit MS Office application without the 're-configuring' issue.

Note that the 'mso.dll' registry value will already be present if a 64-bit version of MS Office is installed. In this case the value should not be deleted or renamed. I just started taking visual basic 2012.Net seriously, but was face with the same problem stated here some time ago, but trust me the solution was not easy at first. However, after reading, trying to solve and understand why this problem exit in the first place I realised the only solution is to install the 32 bit version of Microsoft.ACE.OLEDB.12.0 before you could connect making the application database section versatile.

My developers here let’s try to be precise in answering each other’s questions since they form base for solution(Knowledge base support) to our new developers around. Secondly, I believe Microsoft wishes to allow our application to run on all Microsoft OS platform since 64 bit application is limited to its kind only whiles 32 bit plat form can work out on either 64 bit or 32 bit platform. Has anyone had any success with Applied Math NV's solution using 64-bit Office 2013, W7?

In this case, following the installation of the 32-bit MSA 2010 redist, there is no: HKLM/SOFTWARE/Microsoft/Office/14/Common/FilePaths/mso.dll registry entry, but there are both: HKLM/SOFTWARE/Wow6432Node/Microsoft/Office/14/Common/FilePaths/mso.dll HKLM/SOFTWARE/Wow6432Node/Microsoft/Office/15/Common/FilePaths/mso.dll Following the procedure as written now and deleting/renaming: HKLM/SOFTWARE/Microsoft/Office/14/Common/FilePaths/mso.dll after installation of the 64-bit driver causes all SSIS/MSSQL operations using the driver to fail. Has anyone had any success with this scenario? What does the `/passive` switch actually do? This is quite stupid.

64 Bit Database Driver

For our desktop application, we use ADO to communicate with an Access database and are now considering to make a 64 bit application out of it. However this may not run since we cannot control what kind of Office is installed on the client PC. It seems that the only valuable solution is to drop ADO altogether and use e.g. SQLite is a good alternative, but keep in mind that there are two different sets of assemblies, one for 32-bit and one for 64-bit.

Your installer will need to determine which set to install with your app. Paul Microsoft MVP (Visual Basic). This is quite stupid.

For our desktop application, we use ADO to communicate with an Access database and are now considering to make a 64 bit application out of it. However this may not run since we cannot control what kind of Office is installed on the client PC.

It seems that the only valuable solution is to drop ADO altogether and use e.g. SQLite is a good alternative, but keep in mind that there are two different sets of assemblies, one for 32-bit and one for 64-bit.

Your installer will need to determine which set to install with your app. Paul Microsoft MVP (Visual Basic) We would only have one target, since supporting both 32 and 64 bit is quite some work. In theory it would be a matter of recompilation; in practice it takes a lot more effort.