- ACCESS 2002 RUNTIME INSTALL DOWNLOAD DRIVERS
- ACCESS 2002 RUNTIME INSTALL DOWNLOAD UPDATE
- ACCESS 2002 RUNTIME INSTALL DOWNLOAD PATCH
Or you can replace the DLL, and probably rip open the Jet Database Engine vulnerability.
ACCESS 2002 RUNTIME INSTALL DOWNLOAD UPDATE
So you have two worse choices: Either you have to uninstall the complete security update (see below) and are unpatched.
ACCESS 2002 RUNTIME INSTALL DOWNLOAD PATCH
If an old version of the DLL is now copied to the Windows subfolder syswow, the Jet Database Engine vulnerability is still open (the patch is neutralized). The problem: Microsoft has updated the msrd3x40.dll file to fix vulnerabilities in the Jet Database Engine (see my blog post Patchday: Updates for Windows 7/8.1/Server Jan. Note: The file msrd3x40.dll belongs to the Jet Database Engine, as you can see within this Microsoft document. The DLL is located in the Windows subfolder syswow (see also this Microsoft article). After that the Access 97 database was readable again. Someone simply replaced the msrd3x40.dll v.7 from Januwith an older version. Within this MS Answers forum thread another user posted a (less riskier) workaround. But this is risky, because those updates fixes critical vulnerabilities (for instance a PowerShell remote execution flaw). Uninstalling the Windows January 2019 updates will cure the issue. Later I found at Microsoft Answers this forum thread, obviously startet from the same developer (I guess, it’s blog reader Ollat). German blog reader Ollat also noticed, that the data base error “unknown database format” only occurs, if data table fields are longer as 32 characters.
ACCESS 2002 RUNTIME INSTALL DOWNLOAD DRIVERS
It can end in a night mare (mission impossible), because the runtime environment for the later version of data base drivers has significant changed. There was the feedback, that it will be risky, to convert a bigger Access 97 data base to the new Access 2007 data base format. I also discussed this idea within the comments of my German blog. But this is not possible for customers, who don’t have access to the source code.
Within the forum thread it is advised to convert the Access 97 database to the Access 2007 database format. Another user wrote, that he received a ‘Runtime Error 3343 Unrecognized database Format’.
The same problem we have on Windows 7 after the KB4480970 installation of January 8thĪddendum: Later on I received the information, that this error occurs, if a database has fieldnames with more than 32 characters. How I can get support for this accident ? Removing the KB4480116 the issue disappears. The exception starts on msvc100.dll provided by VS 2010.
The post is written from the developer’s point of view and contains the following information.Īfter installing in Windows 10 the KB4480116, our application ( developed in VS2010 with Microsoft Access 97 database MDB ) detects an error “unknown database format” when accessing to Access 97 database. He linked to this forum post, where he blamed Windows 10 update KB4480116 and the Windows 7 update KB4480970, released on January 8, 2019. He wrote:Ĭaution! Since the update our software does not work anymore, which uses itself with Access 97 databases.Īre there similar cases? Can’t find anything on the net… The first message on this issue reached me from blog reader Ollat in this comment within my German blog (thanks for that).
0 kommentar(er)
