How To Check Access Version 32-bit Or 64-bit
Emelia Lute
I inherited a 2013 ms access db file but i do not know if the user created it with a 32- or 64-bit version of access. I know how to check my system settings to see what type my OS and MSO are, but how do I tell how a specific third-party file was created?
Knowing your version helps you choose compatible software add-ons and plugins. Plus, some features may vary between different architectures. So, being aware of your version makes for a smoother experience.
Fun fact: Microsoft Office 1.0, the first-ever office productivity suite, was only available as a 16-bit release for Windows! It included popular applications like Word, Excel, and PowerPoint which revolutionized document creation and data management.
Which version should you choose? If you work with complex files, large databases or memory-intensive tasks, go for the 64-bit version. It provides greater stability and capability to manage large data.
On the flip side, if you use Office mainly for basic activities like writing and creating presentations, the 32-bit version should suffice. It is also compatible with most add-ons and external programs.
To check your Microsoft Office version, utilize the following solutions: Using the File Options and Using the Control Panel. The File Options method allows you to access version information directly within the Office application, while the Control Panel method provides a system-wide view of all installed versions.
Or, for a quicker method, you can simply check the PROCESSOR_ARCHITECTURE environment variable. 64-bit systems will say AMD64 and 32-bit systems should say "x86". To check this you can simply echo it out:
Open one of the programs in Office, such as Word. If the ribbon looks similar to the following image (ribbon tabs with sharp corners), you are using either Office 2013 or 2016. If your ribbon looks different, skip to the next section.
On the Mac, there is no choice between running a 32-bit or 64-bit version of the operating system, since the OS has been 64-bit for several years. Office for Mac 2011 was only available in a 32-bit version, and Office for Mac 2016 is now only available in a 64-bit version.
The installer in the link you get from TDP installs a bridge between the bitness of TDP and Access. You do not have to change Access. Just run the installer in the link that matches the bitness of TDP. (Which in your case is 64-bit)
No, i am not saying that. The bitness of TDP and the Microsoft installer is what needs to match, not the version of Excel. So if you have TDP 64-bit you need to install the 64-bit version of Microsoft Access 2010 installer. note: This installer does not install Access it just installs the ODBC drivers that Microsoft forgot to install when they bundled the later versions of office.
I know before submitting, it had plenty of articles regarding this, but I still cannot get Access to even get the updated 64 bit engine installed while it has the 32 bit access application, so hopefully if I can get around that somehow, toad should have no problem connection.
So, let me give you some confidence. Yes, you can use TDP 64-bit with 32-bit Office. All of us use this combination here. I started out using Office 64-bit, but I concur it is too buggy so I went back to 32-bit Office.
The Microsoft Access 2010 and 2016 Runtime redistributable happen to install the necessary drivers. That is why it is important to use the installer that matches the bitness of TDP. This way the installer will install the ODBC driver of the same bitness. Microsoft handles the rest. They support using 64-bit ODBC driver with 32-bit Excel or Access file.
I suspect that there are remnants of Office 32-bit installed. Go to Add/Remove Apps and search for anything that has Office or 2010 and see if you see anything listed. The message box above says that it still thinks 32-bit office 2010 is installed as well as 32-bit Access runtime 2016 (note that is not Access itself just runtime files)
Once you clarify the procedure through your webex, please let us know how to do it. I have the same problem and having to uninstall and reinstall the entire Microsoft Office 2010 32 bits just to install a few 64 bit ODBC drivers sounds unreasonable (but then again, when you are Microsoft, do you have to be reasonable?)
I built a powerbi report and it worked several times refreshing data from same excel source files. Then I get an error saying something about 64 bit not matching... so I followed the link to microsoft site that said needed to match 64 bit if that's what my computer needs... so I uninstall P-Bi and reinstall 64 bit version and it still won't work.. so i read it again and install Microsoft access 64 bit and still does not work... so I uninstall both p-Bi and access and reinstall both 32 bit versions and get another errror - the External table is not in the expected format.... so here I am...
First error was - Microsoft Access: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. The 64-bit version of the Access Database Engine 2010 Access Database Engine OLEDB provider may be required to read 'XY_Create.mdb'. To download the client software, visit the following site: =285987."
I know recently in Dec, 2020 I think, one could now connect to MS Access tables via Pro. I've been trying to get this to work and unable to see the ODBC connection to the Microsoft Office 12.0 Access Database.
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...
1) I see you have the Microsoft Access Database Engine 2016 Redistributable installed on your system in addition to MS office? This needs to match the 32bit or 64bit installation of Office - please confirm. Once you click the download button you will have the option to select the version or just download both.
I did get this to work when I had the 64 Bit Version of Office 365 installed with the 64-bit version of the Microsoft Access Database Engine 2016 Redistributable. On another system with the 32-bit versions installed it did not work. I will put a support case in with ESRI for a possible bug.
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.
It is my understanding that ArcGIS Pro requires the 64-bit Microsoft Access Database Engine 2016 Redistributable be installed as it is a 64-bit application even when running a 32-bit version of office. I now have both the 32-bit and 64-bit version of the Microsoft Access Database Engine 2016 Redistributable installed and no issues yet.
See that's what I've been doing and I'm unable to see that. I've been doing both on the C drive via quiet mode. I haven't tried it in /passive at all, but heard that wasn't the best way. The biggest issue as I mentioned, is when doing the x64 it then prevents Access itself from opening up and causes an error. This is where I'm at a loss. So it seems maybe something else is going on in the background then if you can get it to work and I am not able to see that.
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.
After further investigation, it appears that error indicates a mismatch between 32-bit and 64-bit versions. We have made many attempts at changing our ODBC connection to correct this mismatch, but to no avail. Any thoughts or recommendations on fixing this would be appreciated.
Now what we noticed was the BenchAccess1720 sample file is, indeed, linked to an SQL database and NOT an Access database. I converted our Access Database over to an SQL database and managed to get things running again, however, this is NOT our preferred solution.
The truth is that the solution they give on some sites to install access and powerbi with its two versions in 32 bits, seems to me a PARCHE. Many companies install their office 365 with 32 bits and then to work with powerbi, the 64-bit version is much more agile... I don't know how there are still people working with the 32-bit version.
The 64-bit versions of Windows use the Microsoft Windows-32-on-Windows-64 (WOW64) subsystem to run 32-bit programs without modifications. The 64-bit versions of Windows don't provide support for 16-bit binaries or 32-bit drivers. Programs that depend on 16-bit binaries or 32-bit drivers can't run on the 64-bit versions of Windows unless the program manufacturer provides an update for the program.
There may be considerations that affect a program's compatibility or performance. You can determine whether a program will have compatibility or performance issues by testing the program on one of the 64-bit versions of Windows.