The IBM i Access for Windows OLE DB Providers, along with the Programmer's Toolkit, make IBM i client/server application development quick and easy from the Windows client PC. The IBM i Access for Windows OLE DB Provider component gives IBM i programmers record-level access interfaces to IBM i logical and physical DB2® for i database files. In addition, they provide support for SQL, data.
Jul 20, 2017 I recently got a new laptop and had to go through the ritual of reinstalling all my programs and drivers. I sometimes work with SSIS locally to import data from Excel and occasionally do demos with Power BI where I read from an Access database so I needed to install the ACE OLE DB provider. During my recent conversation about Oracle linked server with one of my client, I learned something new about “Microsoft OLE DB Provider for Oracle”. This blog has highlights of a lengthy conversation. Important download details: Installing the Microsoft OLE DB Provider for Visual FoxPro 9.0 on a computer that has a previous version of the Provider causes this version to replace the previous version. Thanks for your answer, very useful. I have Office (2016) 64-bit and SQL 64-bit AND the corresponding connector Microsoft.ACE.OLEDB.16.0. However I was getting the message 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine.' I recently got a new laptop and had to go through the ritual of reinstalling all my programs and drivers. I sometimes work with SSIS locally to import data from Excel and occasionally do demos with Power BI where I read from an Access database so I needed to install the ACE OLE DB provider.
High Performance, Reliable Access to Oracle Databases
OLE DB is a Microsoft data access standard accessed through ActiveX Data Objects (ADO), Visual C++, and any client that can use OLE DB. The goal of the Oracle Provider for OLE DB is to have a high performance and rich feature mechanism for data access to Oracle databases
The Oracle Provider for OLE DB allows high performance and reliable access to Oracle databases for ADO- or OLE DB-enabled applications. Current ADO and OLE DB programmers can easily migrate to the Oracle provider because it complies with the OLE DB specification. Additionally, the provider allows access to Oracle-specific features, including PL/SQL stored procedures, LOBs, and RAC. The Oracle OLE DB Provider supports transaction enlistment through the Oracle Services for MTS. The Oracle Provider for OLE DB also offers full support for .NET via the Microsoft OLE DB .NET data provider. With OLE DB .NET, applications can access the Oracle database from any .NET programming language.
Oracle Provider for OLE DB 12.1.0.2 now supports the IRowsetFastLoad interface, which enables fast memory-based bulk-copy operations in the Oracle database. This interface also works with the SQL Server Integration Services fast-load functionality to permit rapid ingestion of large amounts of data to the Oracle database.
I've got a 32 bit .net 2.0 app that uses the Jet OLEDB 4.0.
It runs fin on Windows 8 32 bit, but not on the 64 bit. on 64 bit I'm getting an error:
'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine. at System.Data.OleDb.OleDbServicesWrapper.GetDataSource(OleDbConnectionString constr, DataSourceWrapper& datasrcWrapper)
I am aware that you can't use that database (driver) with a 64 bit EXE. However I've not read anything about it not working with the 32 bit exe.
What I tried:
- Verified that msjet40.dll is in the 'C:WindowsSysWOW64msjet40.dll' directory and registered it with RegSvr32.
So I think (hope) that if I can install the database support it'll just work.
Problem is, I can't find any place to download it.
2 Answers
On modern Windows this driver isn't available by default anymore, but you can download as Microsoft Access Database Engine 2010 Redistributable on the MS site. If your app is 32 bits be sure to download and install the 32 bits variant because to my knowledge the 32 and 64 bit variant cannot coexist.
Depending on how your app locates its db driver, that might be all that's needed. However, if you use an UDL file there's one extra step - you need to edit that file. Unfortunately, on a 64bits machine the wizard used to edit UDL files is 64 bits by default, it won't see the JET driver and just slap whatever driver it finds first in the UDL file. There are 2 ways to solve this issue:
- start the 32 bits UDL wizard like this:
C:Windowssyswow64rundll32.exe 'C:Program Files (x86)Common FilesSystemOle DBoledb32.dll',OpenDSLFile C:pathtoyour.udl. Note that I could use this technique on a Win7 64 Pro, but it didn't work on a Server 2008R2 (could be my mistake, just mentioning) - open the UDL file in Notepad or another text editor, it should more or less have this format:
[oledb] ; Everything after this line is an OLE DB initstring Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:PathToThedatabase.mdb;Persist Security Info=False
That should allow your app to start correctly.
fvuMicrosoft Jet 4.0 Ole Db Provider Download
fvuMysql Ole Db Provider Download
Make sure to target x86 on your project in Visual Studio. This should fix your trouble.