Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Acc 2000 Engine bugs/behavior change in patches...

Status
Not open for further replies.

lameid

Programmer
Jan 31, 2001
4,212
US
I may just be dense in my search abilities but I am having trouble finding any documentation on query behavior changes in Access 2000 caused by patches....

Specificially, Sr1 to SP3.

Sadly at this company if you can load Access 2000 but it is not patched by the system past SR1. Other licenses involve an approval process... Being a sane person I patched my Access 2003 to SP3 without blinking. But when a user got different results with Access 2000 I checked and saw it was only SR1... I knew that was the problem. I subsequently patched to Sp3 and the results are the same.

I skipped from 97 to 2003 so I missed out on this fun. Any pointers would be much appreciated. While I'm contracting here, I can twist arms to have the end users manually apply Service Packs but after that it would be great if the autoupdate tool did it... Hence I want something firmer than I observed this difference.
 
Access 2003 SP3 introduced several bugs into Access and so there are several "hotfixes" out there which you will likely need to apply to return sanity to you.

Here's one of them:

And Access 2000 shouldn't have a problem with its patches. Those were okay.

Bob Larson
Free Access Tutorials and Samples:
 
I haven't experienced any of the bugs requiring a hotfix... However the query behavior DID change from Acc 2000 SR1 to Acc 2000 Sp3. I am thinking it has something to do with the version of Jet 4 for the Service Packs but never got back around to looking into it. The only thing I am aware is that some uses of Outer Joins can cause inappropriate query results but that does not explain the change to me. At some point I really need to upsize to a SQL incarnation and test the queries to see if there is an inconsistency between the SQL and patched Jet resultset....

I do vaguely remember having to patch in order to have the Jet Engine return correct results... I am so far removed from that incident I do not remember the specifics like Access 97 or 2003, or did I have a trial period of 2000 and dump it? I remember bad results, patch, working... What disturbs me is that I can't find anything on query behavior chaning.... Maybe I should search on Jet changes itself... But alas, MS doesn't keep the entire KB alive, so who really knows.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top