Download Microsoft Access Engine 2010
Clarence Pariseau
First I've successfully made the connection to use Excel tables in Pro via ( -blog/products/arcgis-pro/data-management/guide-to-connecting-to-excel-fi...). This of course required me to use the 32-bit accessdatabaseengine.exe from Microsoft and doing the silent install on my C:drive which worked.
Is there something I'm missing here? We are using MS 365 for Enterprise and in Program and Files it does show that the 32-Bit accessdatabaseengine.exe is installed (as I can now use excel tables in Pro).
I looked at that, and it seems that method would work to import the tables from Access, however, our access tables are live and constantly update and so I'd like to find away for it to work as it does in ArcMap unfortunately...
Yes this is what I have been doing. We're using the 32-Bit MS Office 365 here. I can't use the 64-bit because after installing it, Access fails to open, so I had to remove it each time I tested the 64-bit Microsoft engine. The 32-bit one allows Access to open, but I do not see as shown above, any of the Microsoft Database Engine options in the ODBC Database Connect.
I just tried it again and for some reason I was able to see the MS Office 12.0 and 16.0 now. However, the issue is the same that when installing the 64-bit, I can no longer open access. Using the 32-bit one I am, but then I can't see the MS Office 12 or 16 in Pro:
Since you are using Office 365 you should be able to download and install the 64-bit version of office this may eliminate the compatibility issue. I do not have access to a 64-bit version until this evening to confirm if you can still open Access with the 64-bit version of Microsoft Access Database Engine 2016 Redistributable installed but will check it out tonight. I know the drivers were showing but I did not try to open Access.
On Monday, October 12th, Microsoft announced a new data engine option for its popular Microsoft Access database. With the upcoming release of Microsoft Access 2000, users and developers will have the choice of two data engines in the product: an improved version of the existing Access engine, called Jet, or the Microsoft Data Engine (MSDE), which is compatible with Microsoft SQL Server 7.0.
Since the announcement, many questions have arisen regarding the differences between Jet, MSDE and SQL Server, as well as when to use which engine. We thought we might try to make the distinctions between these data sources a little easier to understand by detailing the threeoptions, offering usage scenarios, and detailing how to move data from one solution to another.
The second component is the data engine. Before Access 2000, users and developers used the Jet data engine. In the next version, users and developers will be given a choice of data engines. They can continue with an improved version of Jet 4.0, or MSDE.
Jet 4.0
Jet 4.0 is the default data engine for Access 2000, and is much improved over Jet 3.51, the engine in Access 97. Some of the major enhancements in Jet 4.0 are full UNICODE support, row-level locking, compatibility with SQL Server, Jet/SQL Server 7.0 bi-directional replication, enhanced replication conflict resolution and a native OLE DB provider.
If you are developing or using Access in an enterprise environment, MSDE is the recommended data engine. Even if your current needs are not enterprise level, using the Access front-end with the MSDE back-end will help ensure that your database is in the optimal position for scaling as your business needs grow.
Enterprise applications require scalability, security and robustness, which can be implemented with MSDE but not with Jet. For example, if your application needs transaction support, even in the event of a network, server, client computer, or client application crash, then you will want to use MSDE. Conversely, the Jet engine does not support atomic transactions: it does not guarantee that all changes performed within a transaction boundary are committed or rolled back.
Jet is easier to use and administer than MSDE, making it a good choice for new and relatively simple database applications that do not have compatibility concerns with SQL Server. It has low resources for memory and disk and requires nearly zero administration. Jet is also the default database option for Access 2000. A database created using the Jet engine can always be upsized later to SQL Server using the Upsizing Wizard.
MSDE is the right engine for systems that involve important transactions, such as financial applications, or for mission critical applications that need to be up 24 hours per day, seven days a week, such as the Internet. The more important the database, the more likely you are to choose MSDE.
Were the SQL Agent Jobs modified in any way? Did you double-check that the job step properties for the SSIS package have the package marked to run in 32-bit mode? That would be my first guess; is that something modified the job definition and now it is running in 64-bit mode and unable to access any 32-bit drivers/providers.
I suggest building one of more small SSIS packages that access Excel like your production packages. If you read Excel, build a package that reads a value from one cell and logs it. If you write to Excel, build another small package that writes the date and time to a spreadsheet.
I needed both the 32-bit and the 64-bit adapters to cover my various use cases. I started by installing the 64-bit Microsoft Access Database Engine 2010 Redistributable. If you have ever attempted this, you know there is a secret. You cannot install the 2010 Access database engine with a different processing architecture (bittedness) from your Office install (or install both versions of the 2010 Access database engine) without a workaround. If you try, you will get an error message.
df19127ead