Install Microsoft Access 2013 32 Bit Runtime Print
Modified on: Thu, Aug 5, 2021 at 5:52 AM
How lớn Install Microsoft Access 2013 32 Bit RuntimeThough Microsoft put Windows 7 on the end-of-live junk heap in January, lots of people are running this operating system that is no longer grumpygourmetusa.comed by Microsoft for security vulnerabilities and patches. There"s (at least) one remaining problem that a few folks will face - particularly if they have sầu done in-place upgrades from Windows XPhường and/or 7 khổng lồ Windows 10. It has lớn bởi vì with Microsoft Access.
Bạn đang xem: Microsoft access
Though the frequency of serious problems has dropped considerably as hams have moved khổng lồ Windows 10, we still get calls from customer running Windows 7 (or in some cases, after an in-place tăng cấp from Windows 7 khổng lồ 10) where customers complain that Logbook is slow. We often advise them about how to upgrade to Access Runtime 2013 32-bit. After the customer creates a new database and restores their log lớn it - problem solved!
The purpose of this post is lớn raise your awareness to lớn this problem. I"ll describe what you can vì chưng & what our plans are lớn deal with the problem.
Microsoft Access was first introduced to lớn the market in 1992 after Microsoft acquired FoxPro (& parts of FoxPro were used lớn create Access). With this initial v1.0 release, Access was built on something called the Microsoft Jet Database Engine v1.0. Subsequent releases of Access also included an updated version of Jet. Access 2.0 included Jet 2.0... & so on.
The following chart demonstrates the progression of Access và Jet over the years.
The first thing is - I have sầu no idea why so many copies of the same file are required by Windows. I"ve sầu never been able to understand why they vì chưng this. But, there is something else that we can notice. Even though these files have sầu different dates, they have the same tệp tin name. These are the same versions.
You can tìm kiếm for your version by going to Windows File Explorer & (in the upper right) tìm kiếm for "msjet*.dll" (without the quotes). We can see that - on my fully up-to-date Windows 10 computer - I"m running on Jet v4.0. From the chart above sầu, I can see that this was released in grumpygourmetusa.com of Access 2000 và Access 2003. That was 17-đôi mươi years ago!
What version is in your operating system? Hold that thought...
The most important observation is that these files are in the C:/Windows directory structure. Stated another way - these files are installed as part of the operating system. That means that software you install on this computer will not be allowed to lớn make changes to lớn the nội dung of the Windows operating system. So for software lượt thích Ham Radio Deluxe cộ - it"s a problem that we can"t fix as long as the database is running on Access.
As mentioned before, we get customers complaining that Logbook is slow. When we investigate this, it"s pretty easy khổng lồ find that this is the cause of the problem.
A while back, I wrote a post on our peer grumpygourmetusa.com forums entitled - "For those reporting "slow" performance of Logbook.."
Here are the steps I advised customers khổng lồ take if they feel that Logbook performance is slow:
In Logbook...
Xem thêm: Ví Điện Tử Momo Là Gì, Nhận Khuyến Mại Từ Ví Điện Tử Momo, Ví Momo Là Gì
> clichồng on "Manager"; this opens up the Logbook Databases manager
> cliông xã on "ODBC Administrator"; this opens up Windows 32-bit ODBC Administrator
...among mỏi other things, you should see Microsoft Access Driver và... if you have a reasonably current version of Microsoft Access Runtime on your machine, it will show "*.mdb, *.accdb"
NOTE: In the above image, the logbook database called "HRD Logbook - Access" is using an old Access ODBC driver. I moved all my data out of that và into the logs shown below it to lớn improve the performance of my own installation of Ham Radio Deluxe pháo.
...if you vì not see these two database file types there, then we need to get you off of a 20+ year old version of the Access Runtime.
So if this applies to you... do this:
> use the database backup utility in Logbook khổng lồ make sure you"ve got your latest QSOs backed up
> Please tải về & install the Microsoft Access Database Engine 2013 driver. CAUTION: Please make sure you download and install the 32-bit version (AccessRuntime_x86_en-us.exe) from here: Access Runtime 2013
> Install that 32-bit version of the 2013 Access Runtime (the newer versions have sầu compatibility problems; don"t try lớn use them).
> Once that"s installed... kiểm tra the ODBC Administrator as we did before (you should now see this new Microsoft Access Driver in there with *.mdb, *.accdb in there.
> Create a br& new log
> Make sure the WSI check goes khổng lồ this new log và no longer checks the old log
> Restore your backup khổng lồ this new log
> Use this new log & close the old one.
Feedbaông chồng from customers about this is almost 100% effective.
Finally, given that this is part of the operating system, it"s not something we can change with our installation of Ham Radio Deluxe. That is - we can"t fix the version of Jet. We can provide guidance about how to lớn fix it.
That said, we DO want khổng lồ move sầu away from Access (and Jet) for a number of reasons. Reason #1 - all the problems referenced above. Reason #2 - we need to have sầu a version of Ham Radio Deluxe cộ that is not dependent upon Windows-specific foundations in order to create versions that will run on Linux or Mac. It is in our plan lớn move sầu off of Access.
This can also help for cases where customers get the following errors:
"HRD Log Book - Access the specified DSN contains an architecture mismatch between the driver và application"
