Reinstall microsoft jet oledb 4.0

Rebuilding these apps for x86 is quite the task, and hasn't been working as easily as its stated. Even reconfiguring each user's machine is going to be a task.

I don't see additional posts by timorris on this thread, has he given up as well? Has the solution stated above, installing the bit Microsoft Access Database Engine Redistributable, been tested on a Windows 7 bit platform with Access , by Microsoft?

For each of our users, this requires uninstalling the bit Office in our case , installing the redistributable and then reinstalling the bit Office. I have searched for the Microsoft Jet 4. Following the directions to check the version installed, I get 4. Using the test. Substitute a period for dot - I can't provide a link yet because have not yet given me permission. Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access.

Search related threads. Remove From My Forums. Answered by:. Archived Forums. Details required :. Cancel Submit. Daniel Pineault MVP.

Can't you install a bit oledb for those clients? How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. In reply to Daniel Pineault's post on July 12, I am not finding solution What should I do? In reply to amithkulkarni's post on July 12, From the solution explorer right-click your project then click Properties 2.

Click the Build tab 3. Re-build your solution i can access my database. Naren Websoft Oct am. There is indeed no 64 bit version of Jet - and no plans apparently to produce one. Posted Sep am OriginalGriff. ACE requires Access runtime engine, I think, whereas if a Jet solution can be contrived, there is no requirement to have Access present on the local machine, since Jet used to come with Windows. Thus I would hope that Solutions 1 and 2 continue to work for a long, long time.

If not, my solution road map will probably suffer great harm. I am still looking, it seems critical to stay on top of this rather then get left for dead by MS.

Bill Benson. Posted 3-Mar am Member Posted May am KK shah. Add your solution here. OK Paste as. Treat my content as plain text, not as HTML. Existing Members Sign in to your account. This email is in use. Do you need your password? Submit your solution! When answering a question please: Read the question carefully. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.

Although a more optimal solution is to simply recompile as suggested above, that requires access to the source code. In my case, I only had the finished. It uses CorFlags. Net SDK to change the loading characteristics of the application. You're done! This sets the starting flags for your program so that it starts in 32 bit WOW64 mode, and can therefore access microsoft.

There is indeed no 64 bit version of Jet - and no plans apparently to produce one. However, you may be able to switch the project to 32bit in the Express version I haven't tried and don't have installed in any flavour anymore. Maybe it's time to scrap Access databases altogether, bite the bullet and go for SQL server instead? In older versions of IIS, you will not find Advance Settings so to enable Enable bit Applications you have to execute the following commands:.

I haven't changed any IIS setting and not installed any extra software. I know that I have this problem over and over when I deploy my application on a new server because I'm using this driver to connect to a Excel file. So here it is what I'm doing lately. There's a Windows Server R2, I install the Access drivers for a x64 bit machine and I get rid of this message, which makes me very happy just to bump into another.

This one here below works splendidly on my dev machine but on server gives me an error even after installing the latest ODBC drivers, which I think this is the problem, but this is how I solved it.