JET Version for Access 2002 (2002 SP2)

Topic

New Reply

As a modal user, I could safely ignore the Jet version of my Access XP data base. No longer so, it seems. I tried to execute a (not so complicated) query, which worked, but could not be saved. Access shut down rather (un)graciously. I colleague suggested that I should inspect the Jet Version. Office XP (aka known as Office 10) was installed on a Win/Me system about 2 years ago. But regularly maintained as suggested by MS maintenance check. The actual version is SP2.

I thought, having read some documentation, that the Jet Version should have been V4. Inspection (Access Help -> Info -> SystemInfo -> Ofice 10 Apllications -> MS Access 2002 -> JET Kernel) surprised me by telling that JET 4.0 (its path) was NOT available. (Neither was ODBC) However there was a path entry for JET 2.x and JET 3.x!

So I checked the Registry (RegEdit) and found (HKEY_LOCAL_MACHINESoftwareMicrosoftJET) and found TWO entries: one for JET 3.5 and one for JET 4.0. The JET 4.0 entry contained (Engines) a map for JEt 2.x, JET 3.x and JET 4.0. The JET 3.5 key showed (Engines) entries for JET 2.x and JET 3.5, Almost the references found by Access Systeminfo. I also found that the JET 3.5 key was located BEFORE the JET 4.0 key. (alphanumerical order or intentionally?) It looks to me as if Access picked up the first available Key in the registery.

Can someone clarify to me how I can rectify the situation? Is it correct that Access 2002 should use JET 4?

I also found a KBS article 282010 (http.//support.microsoft.com/default.aspx?scid=kb;en-us;Q282010) telling that the JET 4.0 should be updated with SP6. Will this be of any help?

I’m rather ignorant (remember modal end-user) in Registry matters, so please if any manipulation has to be done, try to be specific (even elementary)

Reply | Quote

Replies

I don’t think you really have a problem – at least my install on Win ME shows the Jet 4.0 Path as not being available either. In addition, the registry only has one entry under Jet, that being 4.0 – under engines it does show Jet 2.x, Jet 3.x and Jet 4.0 in that order. As to the version number of Jet, an upgrade to SP6 wouldn’t hurt things any – you can find it here, but be sure to get the version for Win ME. However you might want to check the version of MSJET40.DLL before you do that. It should be located in C:WINDOWSSYSTEM by default. If you find you have version 4.0.6218.0 then you already have the latest version.

I suspect that your crash in a query was not really a Jet problem, but more probably a Windows ME problem. I’ve run my system in this configuration for about 18 months, and it occasionally will crash out of the blue. You might find some useful info in technet article 284152. If some of this doesn’t make sense to you, please post again and we will do our best to help you out.

Reply | Quote

The JET version on my system was (MSJET40.DLL) was: 4.0.2927.17 Consequently I upgraded it to SP6 (4.0.6218.0), but as you expected , to no avail. The query still won’t be saved. So JET does not seem to be the culprit. I’ll therefore open another thread “Query definition not saved” to present the problem at hand.
But before leaving this thread I still have a couple of questions with this JET matter:
1. How can I be sure that ACCESS uses JET40 and not JET35? Remember both are installed on my system
2. Has anyone an idea where that 35 came from? WinME, Office XP (professional) or VB6 (enterprise edition), the only MS products I have on my system
3. If JET is an Office Component, How come that Microsoft’s Office Maintenance check fails to recognize that I didn’t have the latest version?
4. Can I remove 35, as I can’t see any need for it? And how to do it correctly?

As for 2003 (the year) I wishes anybody looking at this thread all the best, and hopes that he or she can spend in the coming year more time developing applications rather than continuously maintaining and upgrading the software. But I wished that for years already…

Reply | Quote

I have a theory, totaly unproven, that the Jet3.5 registry entry was made by OfficeXP. For one thing, Access 2002 is capable of reading and writing Access 97 (Jet 3.5) databases. The second things is that at least in my case, I don’t have the Jet3.5 DLL installed. Another guess, I suspect one of the office apps needs the 3.5 registry entry for some reason. At this point I wouldn’t mess with trying to remove the 3.5 registry entry until it’s clear that it is somehow causing your problem. If you haven’t already, do post the details in a new thread.

Reply | Quote

The theory may be correct, because I converted sometime ago another database from 97 to 2002 format, using access’ utilities.

Details of the problem are posted: Query definitions not saved

When investigating the problem after access shutdown (“click here”) the error is occuring in AppName msaccess.exe (10.0.4302.0), ModName mso.dll (10.0.4219.0).
I also send the error report to MS, but I don’t expect any answer from them, not even a confirmation they received it. (Previous history learned me this)

Reply | Quote