![]() among other things, you should see Microsoft Access Driver and. > click on "ODBC Administrator" this opens up Windows 32-bit ODBC Administrator > click on "Manager" this opens up the Logbook Databases manager Here are the steps I advised customers to take if they feel that Logbook performance is slow: When we investigate this, it's pretty easy to find that this is the cause of the problem.Ī while back, I wrote a post on our peer support forums entitled - " For those reporting "slow" performance of Logbook." So for software like Ham Radio Deluxe - it's a problem that we can't fix as long as the database is running on Access.Īs mentioned before, we get customers complaining that Logbook is slow. That means that software you install on this computer will not be allowed to make changes to the content of the Windows operating system. Stated another way - these files are installed as part of the operating system. The most important observation is that these files are in the C:/Windows directory structure. What version is in your operating system? Hold that thought. ![]() From the chart above, I can see that this was released in support of Access 2000 and Access 2003. ![]() We can see that - on my fully up-to-date Windows 10 computer - I'm running on Jet v4.0. You can search for your version by going to Windows File Explorer and (in the upper right) search for "msjet*.dll" (without the quotes). Even though these files have different dates, they have the same file name. But, there is something else that we can notice. I've never been able to understand why they do this. The first thing is - I have no idea why so many copies of the same file are required by Windows. See the column that says, "DLL file name?" Let's see where those files are located in the file/folder structure of Windows: ![]() On the right, you can see the versions of Access along with the Jet versions. On the left, you can see the versions of Jet. The following chart demonstrates the progression of Access and Jet over the years. Subsequent releases of Access also included an updated version of Jet. With this initial v1.0 release, Access was built on something called the Microsoft Jet Database Engine v1.0. Microsoft Access was first introduced to the market in 1992 after Microsoft acquired FoxPro (and parts of FoxPro were used to create Access). I'll describe what you can do and what our plans are to deal with the problem. The purpose of this post is to raise your awareness to this problem. After the customer creates a new database and restores their log to it - problem solved! We often advise them about how to upgrade to Access Runtime 2013 32-bit. Though the frequency of serious problems has dropped considerably as hams have moved to Windows 10, we still get calls from customer running Windows 7 (or in some cases, after an in-place upgrade from Windows 7 to 10) where customers complain that Logbook is slow. There's (at least) one remaining problem that a few folks will face - particularly if they have done in-place upgrades from Windows XP and/or 7 to Windows 10. Though 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 supported by Microsoft for security vulnerabilities and patches. How to Install Microsoft Access 2013 32 Bit Runtime Solution home Knowledgebase Logbook Install Microsoft Access 2013 32 Bit Runtime
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |