- Access 64 Bit Odbc Driver Download
- Download Microsoft Access 32 Bit
- Microsoft Access Text Driver Download
Active2 years, 2 months ago
- Office 2013 64 bits ODBC Drivers. In order to have available the Access and Excel ODBC 64-bit drivers.
- Installing 32-bit and 64-bit Microsoft Access Drivers next to. A 32-bit or a 64-bit version of the Microsoft Access. DRIVER=Microsoft Access Text.
Hi, I installed Office 2013 Professional 64-bit in order to have available the Access and Excel ODBC 64-bit drivers. However the only one that appears available is.
We currently have a major issue using Microsoft Access Database Engine 2010. The engine comes in 64-bit and 32-bit forms, which is good. However, apparently you need to always install the 32-bit version if the host process is always 32-bit. Fine, we can do this.
Our software deals with a lot of legacy components that are 32-bit, and much of it is in VB6 code, which generates 32-bit assembly. So, we are under the assumption that the driver must also be installed as 32-bit. Indeed, when we install 32-bit drivers on a 64-bit machine, and run our 32-bit applications, it works correctly.
However, the problem begins when Office 2010 64-bit is installed on the system. Trust me, we've tried to educate users that 64-bit Office is largely unnecessary, to no avail. As computers come off the assembly line with 64-bit versions installed, we're unable to keep up with support requests when our software breaks something. Either the 64-bit Office breaks our installation, or our installation breaks their Office version, but it's not pretty either way. A further issue is that non-legacy software will sometimes install the 64-bit drivers (as they should), and the two versions simply do not coexist in any reasonable manner. Either our software breaks, or their software breaks.
So, has anybody managed to find a way to make the 32-bit drivers coexist with 64-bit installations? I have seen that installing with
drharrisdrharris/passive
flag allows the two to be installed, and our installer does use passive. Both are being installed, but once on the system either our software no longer works, or Office constantly repairs its installation. Is there any reasonable way to make this work?9,90855 gold badges3737 silver badges5353 bronze badges
6 Answers
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 'HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice14.0CommonFilesPaths' 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 pathAccessDatabaseEngine_x64.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.
Also if you do not want to use the '/passive' command line parameter you can edit the AceRedist.msi file to remove the MS Office architecture check:
- download and install Microsoft Orca:http://msdn.microsoft.com/en-us/library/windows/desktop/aa370557(v=vs.85).aspx
- unzip the AccessDatabaseEngine.exe or AccessDatabaseEngine_x64.exe file
- open the AceRedist.msi file in Orca
- search for two table rows containing the 'CheckOfficeArchitecture' action and drop these rows
- save the updated AceRedist.msi file
You can now use this file to install the Microsoft Access Database Engine 2010 redistributable on a system where a 'conflicting' version of MS Office is installed (e.g. 64-bit version on system with 32-bit MS Office version)Make sure that you rename the 'mso.dll' registry value as explained above (if needed).
Peter CoppensPeter Coppens
I hate to answer my own questions, but I did finally find a solution that actually works (using socket communication between services may fix the problem, but it creates even more problems). Since our database is legacy, it merely required
Microsoft.ACE.OLEDB.12.0
in the connection string. It turns out that this was also included in Office 2007 (and MSDE 2007), where there is only a 32-bit version available. So, instead of installing MSDE 2010 32-bit, we install MSDE 2007, and it works just fine. Other applications can then install 64-bit MSDE 2010 (or 64-bit Office 2010), and it does not conflict with our application.Thus far, it appears this is an acceptable solution for all Windows OS environments.
drharrisdrharris9,90855 gold badges3737 silver badges5353 bronze badges
I had a more specifc error message that stated to remove 'Office 16 Click-to-Run Extensibility Component'
I fixed it by following the steps in https://www.tecklyfe.com/fix-for-microsoft-office-setup-error-please-uninstall-all-32-bit-office-programs-office-15-click-to-run-extensibility-component/
- Go to Start > Run (or Winkey + R)
- Type “installer” (that opens the %windir%installer folder), make sure all files are visible in Windows (Folder Settings)
- Add the column “Subject” (and make it at least 400 pixels wide) – Right click on the column headers, click More, then find Subject
- Sort on the Subject column and scroll down until you locate the name mentioned in your error screen (“Office 16 Click-to-Run Extensibility Component”)
- Right click the MSI and choose uninstall
kloarubeekkloarubeek
Install the 2007 version, it seems that if you install the version opposite to the version of Office you are using you can make it work.
Matthew DolmanMatthew Dolman95655 gold badges1717 silver badges4343 bronze badges
A similar approach to @Peter Coppins answer. This, I think, is a bit easier and doesn't require the use of the Orca utility:
- Check the 'HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice14.0CommonFilesPaths' registry key and make sure the value 'mso.dll' is NOT present. If it is present, then Office 64-bit seems to be installed and you should not need this workaround.
- Download the Microsoft Access Database Engine 2010 Redistributable.
- From the command line, run: AccessDatabaseEngine_x64.exe /passive
(Note: this installer silently crashed or failed for me, so I unzipped the components and ran: AceRedist.msi /passive and that installed fine. Maybe a Windows 10 thing.)
- Delete or rename the 'mso.dll' value in the 'HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice14.0CommonFilesPaths' key.
Source: How to install 64-bit Microsoft Database Drivers alongside 32-bit Microsoft Office
JahmicJahmic7,03877 gold badges4747 silver badges6060 bronze badges
If both versions of Microsoft Access Database Engine 2010 can't coexists, then your only solution is to complain to Microsoft, regarding loading 64 bits versions of this in your 32 bits app is impossible directly, what you can do is a service that runs in 64 bits that comunicates with another 32 bits service or your application via pipes or networks sockets, but it may require a significant effort.
RafaelRafael2,65611 gold badge1212 silver badges1616 bronze badges
Not the answer you're looking for? Browse other questions tagged 32bit-64bitinstallshieldlegacymsde or ask your own question.
Active7 months ago
Hi i have an application developed on XP with Text ODBC drivers. But when i deployed on Win 7 with office 2007, i have connection issues.
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
i have googled every solutions like installing the following
Microsoft Access Database Engine 2010 Redistributable (32-bit)
2007 Office System Driver: Data Connectivity Components
after all of those, in my datasources(ODBC), it still only shows 'SQL native client/SQL server/SQL server native client'
in the C:WindowsSysWOW64odbcad32.exe
i can see all the x32 drivers, but how can i modify my connection strings to access 32-bit Microsoft Text Drivers or are there any alternative solutions? Thanks
KiddoKiddo3,01244 gold badges4040 silver badges6666 bronze badges
5 Answers
I'm pretty sure it'll work automatically (even on a 64-bit machine) as long as the executing process is 32-bit.
Try recompiling to target x86 specifically.
CameronCameron71.4k1616 gold badges165165 silver badges205205 bronze badges
You need the 64-bit Microsoft Access Database Engine 2010 Redistributable
Then try
for the driver name.
AFAIK, all 64-bit ODBC drivers from the Microsoft Access Database Engine 2010 64-bit Redistributable have slightly changed their driver names, I guess to differentiate them from their 32-bit counterparts.
jumpinjackiejumpinjackie1,13233 gold badges1414 silver badges2424 bronze badges
I had this exact problem and the recompiling to target x86 specifically worked! Note that in order to do this I had to specify the Target CPU in the advanced compiler setting dialog - Project Menu> Properties> Compile tab> Advanced Compile Options button.
Before finding this forum entry I did install the Microsoft Access Database Engine 2010 Redistributable (32-bit) but I don't know if that had any affect on this issue.
As mentioned above, when the executing process is 32-bit (in this case compiling against x86 makes the app 32-bit specific) the application will use the drivers from C:WindowsSysWOW64odbcad32.exe.
Thanks Cameron.
SteveSteve
We were doing this from ASP.Net and got it working on Windows 2012 just by moving the one site into a separate app pool that had '32-bit Enabled' turned on in the advanced settings for the App Pool.
WillWill
Access 64 Bit Odbc Driver Download
A lot of people seem desperate here, I want to offer a few solutions. But, first I want to highlight what a dated proprietary trash idea from the 90s this is.
- Use Unix ODBC to host the text file from Linux which the docs (seem to) claim to support an implementation of the Microsoft text driver
- A better option would be of course to import the CSV into PostgreSQL.
- I would suggest just doing this with
COPY
and dropping the notion of a CSV. - You can maintain the CSV with PostgreSQL acting as a server with the Foreign Data Wrapper (
file_fdw
).
- I would suggest just doing this with
- If you don't want to run an RDBMS, the modern way would be to use SQLite. This is a great idea if you don't need the server/client model.
Download Microsoft Access 32 Bit
The ODBC->text interface is especially insane, because ODBC doesn't define configuration beyond connection (so I assume there are lots of assumptions there).
Evan CarrollEvan CarrollMicrosoft Access Text Driver Download
39.3k2626 gold badges156156 silver badges269269 bronze badges