MS Service Pack Causing Problem in Access 2000

[Coleen]

We have a database that was originally created in Access 97. It has been
converted into Access 2000. We have multiple users who need to access this
database, so the .mdb currently resides on one of our Networks. When the
main user attempts to open this particular database, it works until she
exits one of the forms, which then throws an error, which is corrupting her
database if she continues. Her service pack is #4. One of my colleagues
and I who have been trying to troubleshoot this problem have Service Pack 2,
and Service Pack 3, respectively. I do not get the error that she is
getting and neither does my colleague (who is using SP2.) We have also
noticed that the version of VBA differs from Service Pack to Service Pack.
We tested by loading a machine with Access 2000 and Service Pack 3, then
another with A2K and Service Pack 4. The error ONLY occurs with Service
Pack 4. It is a critical issue to get this resolved! Has any one heard of
this problem, and/or what can be done to fix Service Pack 4 to work
correctly with A2K? Please help... TIA

Coleen

 

[Bruce M. Thompson]

That's interesting. I didn't know there was a service pack 4. Where was this
obtained? I can't find it at the Office Products Update site. My copy of Office
2000 is up-to-date at SP3.

 

[Coleen]

To be honest, I don't know where the Network guys got the Service Pack 4 -
it is SP4 for Windows, not Access. We did find that the Jet 4 Service Pack
8 which is now available seems to fix all the errors that the Windows SP4
created; evidently Microsoft is aware of the problems it created. Too bad
they don't test THOROUGHLY before releasing products...it would have saved
us three months of trouble-shooting!

 

[Peter Miller]

Coleen,

To be honest, I don't know where the Network guys got the Service Pack 4 -
it is SP4 for Windows, not Access. We did find that the Jet 4 Service Pack
8 which is now available seems to fix all the errors that the Windows SP4
created; evidently Microsoft is aware of the problems it created. Too bad
they don't test THOROUGHLY before releasing products...it would have saved
us three months of trouble-shooting!

No doubt you(they) were using an old jet dll. There were various
applications and updates that included versions of jet later than that
originally released with Office 2000, but earlier than the last
several jet updates. Two problems occurring with this post Access
2000 but pre jet4sp6 jet version involved multi-table queries and new
record generation. If your form had a multi-table datasource, or
subforms or other such features, the problems occuring simply by
record navigation could trigger corruption. Jet4sp8 would fix the
problem, but so would have v7 and v6. The Office service packs would
not.



Peter Miller
____________________________________________________________
PK Solutions -- Data Recovery for Microsoft Access/Jet/SQL
Free quotes, Guaranteed lowest prices and best results
www.pksolutions.com 1.866.FILE.FIX 1.760.476.9051

 

[Tony Toews]

We have a database that was originally created in Access 97.

Also responded to in the m.p.a.conversion newsgroup.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[TimE]

I had a similar problem on a Windows 2000 Pro computer with SP4 installed.

I found that when I uninstalled SP4, that error stopped but I couldn't call any of my Visual Basic functions. I kept getting a 'Function Name Not Known' error. I noticed that SP8 for MS Jet is included in Windows 2000 SP4. I tried our database on two identical laptops running Windows XP and found that it worked on one and not the other. I also found that when I uninstalled SP8 on the one it didn't work on, I got a change identical to the one I got when uninstalling SP4 from the Windows 2000 computer.

Eventually, I traced my problem to a Microsoft Jet 4.0 setting in the problem computer's registry.

The Key;
\\HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\engines\SandBoxMode
contained a value of 2 on working computers, but contained a value of 3 on the problem computer.

There is information on the SandBoxMode on the Microsoft web site at
http://support.microsoft.com/default.aspx?scid=kb;en-us;239482

Hope this helps!

 

[Coleen]

The problem was solved by installing the most recent Jet service packs. The
errors that were occurring were indeed sub-form problems, and multiple table
data sources. Thanks for your advice/info. I appreciate all the help I get
from these news groups Coleen