Looking for:
- Search results - Microsoft Download Center |
- Access 2016 microsoft.jet.oledb.4.0 free download
Join Stack Overflow to learn, share knowledge, and build your career. Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search.
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. On modern Windows this driver isn't available by default anymore, but you can download as Microsoft Access Database Engine 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:.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Ask Question. Asked 8 years, 6 months ago.
Active 4 years, 11 months ago. Viewed k times. I've got a 32 bit. It runs fin on Windows 8 32 bit, but not on the 64 bit. 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. Improve this question. Clay Nichols. Clay Nichols Clay Nichols Not available. Change your EXE project's Platform target setting to x86 so the bit version will work. Hans, my. Is that different from targeting x86? The default target for. Which will make it run as a bit process on the bit version of Windows.
So don't assume anything and check your Platform target setting, x86 is required. I'll take a look at that. If that's the case then wouldn't the 64 bit driver have done the trick for us? Just wondering. Add a comment. Active Oldest Votes. Improve this answer.
I don't have a. I see how to create a blank. Do I create that in the app directory? ClayNichols not all applications use an UDL file, it's just an extra layer of indirection that allows more flexibility in the configuration of the applications.
Maybe your application doesn't need one, the path to the database file could be stored inside the app, or configured by the app in some other way. Did you install the driver I mentioned in the mean time? Because, once you've done that the error should either go away, or change, eg to signal that it can't locate the mdb file.
Yes, I installed that driver. Oh, sorry, yes, I'd already tried that earlier forgot to note that. Tried both the 32 bit version and then uninstalled it and then the 64 bit version. Same error both times. I assume that a 32 bit app needs the 32 bit version, right? Yes it does, and as both drivers cannot coexist you indeed have to deinstall the 64 bits driver before installing the 32 bit driver.
It's not logical that the driver appears to be missing even after you installed the 32 bit driver. Can you try to run the command I mentioned in point 1, in the initial screen you can see all registered drivers, in this case for 32 bits. Do you mean the the command to start the UDL wizard? Show 1 more comment. Make sure to target x86 on your project in Visual Studio. This should fix your trouble.
Kyle Blake Kyle Blake 39 1 1 bronze badge. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Best practices for writing code comments. Featured on Meta. Linked 0. Related Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. Accept all cookies Customize settings.
No comments:
Post a Comment